Generating a contingent action token

ABSTRACT

A method executed by a computing device includes interpreting a request to generate a non-fungible token (NFT) for an object distributed ledger to produce baseline content that includes an obligation provider identifier (ID) and an outcome recipient ID. The method further includes verifying, validity of the baseline content. When the baseline content is valid, the method further includes determining whether a beneficial improvement is provided to a result of a triggered outcome when a hypothetical change to the obligation provider ID is made. The method further includes an outcome evaluation and establishing NFT content based on the outcome evaluation to include the baseline content. The method further includes causing generation of a new block affiliated with the NFT via a blockchain of the object distributed ledger, where the new block includes the NFT content.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to35 U.S.C. § 119(e) to U.S. Provisional Application No. 63/339,843,entitled “UTILIZING A CONTINGENT ACTION TOKEN,” filed May 9, 2022, whichis hereby incorporated herein by reference in its entirety and made partof the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT—NOTAPPLICABLE INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACTDISC—NOT APPLICABLE BACKGROUND OF THE INVENTION Technical Field of theInvention

This invention relates generally to communication systems and moreparticularly to asset reconfiguration and reassignment within thecommunication system.

Description of Related Art

Communication systems are known to communicate data betweencommunication devices of the communication system. The data may becommunicated in one or more of an unaltered form (e.g., raw data from afirst communication device), in an altered form to provide enhancedtransmission reliability (e.g., error encoded), in an altered form toprovide enhanced security of access (e.g., credentialed access,encryption), and in an altered form to enhance communication resourceutilization (e.g., compression). The data may represent a wide varietyof data types including one or more of video, audio, text, graphics, andimages. Text data is widely known to represent text characterdocumentation, financial documents of numerical nature, and/or acombination thereof.

Global enterprise operations are increasingly utilizing communicationsystems to communicate representations of financial affairs. Financialdocuments associated with the financial affairs may includeadvertisements, solicitations, asset pricing information, purchaseorders, invoices, payment transactions, asset distribution information,complex settlement information, financing information, financial marketinformation, asset titling information, transaction guaranteeinformation, global finance trend analysis information, and otherinformation associated with the increasingly complex world of electroniccommerce.

The global velocity of data communication and massive volume of datarepresenting financial documents is ever-increasing and as a result itis a growing challenge to communicate, manipulate, and enhance the datarelated to financial affairs. Such challenges include refreshing anasset base of the financial system (e.g., including detecting growingissues with regards to desired funding levels of the financial system),unlocking untapped asset value (e.g., conversion of one asset type toanother), and rapidly retitling new or re-spun assets (e.g., assigningnew assets, reassigning converted assets).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a communicationsystem in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a device of acommunication system in accordance with the present invention;

FIG. 3 is a schematic block diagram of an embodiment of a server of acommunication system in accordance with the present invention;

FIGS. 4A-4B are schematic block diagrams of another embodiment of acommunication system in accordance with the present invention;

FIG. 4C is a logic diagram of an example of a method of enhancing alegacy asset base in accordance with the present invention;

FIG. 4D is a logic diagram of another method of enhancing a legacy assetbase in accordance with the present invention;

FIG. 5A is a schematic block diagram of an embodiment of a diagnosticmodule in accordance with the present invention;

FIG. 5B is a logic diagram of an example of a method of diagnosing alegacy asset base in accordance with the present invention;

FIG. 6A is a schematic block diagram of an embodiment of an acquisitionmodule in accordance with the present invention;

FIG. 6B is a diagram of an example of acquiring augmenting assets inaccordance with the present invention;

FIG. 6C is a logic diagram of an example of a method of acquiringaugmenting assets in accordance with the present invention;

FIG. 7A is a schematic block diagram of an embodiment of an augmentationmodule in accordance with the present invention;

FIG. 7B is a diagram of an example of utilizing augmenting assets inaccordance with the present invention;

FIG. 7C is a logic diagram of an example of a method utilizingaugmenting assets in accordance with the present invention;

FIG. 8A is a schematic block diagram of another embodiment of acommunication system in accordance with the present invention;

FIG. 8B is a logic diagram of another example of a method of enhancing alegacy asset base in accordance with the present invention;

FIG. 9A is a schematic block diagram of another embodiment of acommunication system in accordance with the present invention;

FIG. 9B is a logic diagram of an example of a method of acquisition ofan augmenting asset bundle in accordance with the present invention;

FIG. 10A is a schematic block diagram of another embodiment of acommunication system in accordance with the present invention;

FIG. 10B is a logic diagram of an example of a method of updating anacquired augmenting asset bundle in accordance with the presentinvention;

FIG. 11A is a schematic block diagram of another embodiment of acommunication system in accordance with the present invention;

FIG. 11B is a logic diagram of another example of a method of updatingan acquired augmenting asset bundle in accordance with the presentinvention;

FIGS. 12A-12E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forservicing a plurality of rived longevity-contingent instruments within acomputing system in accordance with the present invention;

FIGS. 13A-13E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method for rivinglongevity-contingent instruments within a computing system in accordancewith the present invention;

FIGS. 14A-14E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forgenerating a portfolio of blockchain-encoded rived longevity-contingentinstruments within a computing system in accordance with the presentinvention;

FIGS. 15A-15C are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forutilizing a portfolio of blockchain-encoded rived longevity-contingentinstruments within a computing system in accordance with the presentinvention;

FIGS. 16A-16D are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method for updatinga portfolio of blockchain-encoded rived longevity-contingent instrumentswithin a computing system in accordance with the present invention;

FIGS. 17A-17C are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forutilizing blockchain-encoded records for rived longevity-contingentinstruments within a computing system in accordance with the presentinvention;

FIGS. 18A-18E are schematic block diagrams of an embodiment of acomputing system illustrating an embodiment of a method for utilizing acontingent action token within the computing system in accordance withthe present invention;

FIGS. 19A-19B are schematic block diagrams of another embodiment of acomputing system illustrating another embodiment of a method forgenerating a contingent action token within the computing system inaccordance with the present invention; and

FIGS. 20A-20B are schematic block diagrams of another embodiment of acomputing system illustrating another embodiment of a method forutilizing a contingent action token within the computing system inaccordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a communicationsystem 10 that includes a legacy system 12, a plurality of Naugmentation systems 14, a conversion server 16, a transactional server18, a control server 20, one or more data sources 26, and a network 28.Alternatively, the communication system 10 may include any number oflegacy systems 12 and any number of servers 16-20.

The legacy system 12 includes a plurality of user devices 32, aplurality of subscriber devices 34, a portion of the network 28, and alegacy server 22. Each user device 32 may be implemented utilizing oneor more portable communication devices. Examples of portablecommunication devices include a smart phone, a basic cell phone, a Wi-Ficommunication device, a satellite phone, and/or any other device thatincludes a computing core (e.g., providing processing modulefunctionality), one or more wireless modems, sensors, and one or moreuser interfaces, and is capable of operating in a portable modeuntethered from a fixed and/or wired network. For example, a particularuser device 32 is implemented utilizing the smart phone, where the smartphone is utilized by a user associated with the legacy system 12. Atleast some of the user devices 32 are capable to communicate dataencoded as wireless communication signals and/or wireless locationsignals with the portion of the network 28 associated with the legacysystem 12 and/or directly or indirectly to other user devices 32 and/orto at least some of the user devices 34.

Each subscriber device 34 may be implemented utilizing one or morecomputing devices. Examples of portable computing devices includes alaptop computer, a tablet computer, a handheld computer, a desktopcomputer, a cable television set-top box, an application processor, aninternet television user interface, and/or any other device thatincludes a computing core a (e.g., providing the processing modulefunctionality), one or more modems, sensors, and one or more userinterfaces. For example, a particular user subscriber device 34 isimplemented utilizing the laptop computer, where the laptop computer isutilized by a subscriber associated with the legacy system 12. Thesubscriber devices 34 are capable to communicate data that is encodedinto wireless and/or wired communication signals via the portion of thenetwork 28 associated with the legacy system 12 and/or directly orindirectly to other subscriber devices 34 and/or to at least some of theuser devices 32.

The components of the communication system 10 are coupled via thenetwork 28, which may include one or more of wireless and/or wirelinecommunications networks, one or more wireless location networks, one ormore private communications systems, a public Internet system, one ormore local area networks (LAN), and one or more wide area networks(WAN). For example, the network 28 is implemented utilizing the Internetto provide connectivity between the legacy system 12, the plurality ofaugmentation systems 14, the one or more data source 26, and the servers16-20. The wireless location networks communicate wireless locationsignals with the user devices 32. Each wireless location network may beimplemented utilizing one or more of a portion of a global positioningsatellite (GPS) satellite constellation, a portion of a private locationservice, a wireless local area network (WLAN) access point, a Bluetooth(BT) beacon and/or communication unit, and a radiofrequency identifier(RFID) tag and/or transceiver. Each wireless location network generatesand transmits the wireless location signals in accordance with one ormore wireless location industry standards (e.g., including synchronizetiming information (i.e., GPS), and a geographic reference identifier(ID) (i.e., a beacon ID, a MAC address, an access point ID such as awireless local area network SSID)).

The wireless communication networks of the network 28 include one ormore of a public wireless communication network and a private wirelesscommunication network and may operate in accordance with one or morewireless industry standards including 5G, 4G, universal mobiletelecommunications system (UNITS), global system for mobilecommunications (GSM), long term evolution (LTE), wideband code divisionmultiplexing (WCDMA), and IEEE 802.11. For example, a first user device32 communicates data encoded as wireless communication signals with a 4Gpublic wireless communication network of the network 28 and a seconduser device 32 communicates data encoded as wireless communicationsignals with a Wi-Fi wireless communication network of the network 28.

The legacy server 22 includes at least one processing module 44 and atleast one database 30. The processing module 44 processes controlmessages 36 and data messages 38 via the network 28 with one or more ofthe user devices 32, the subscriber devices 34, the augmentation systems14, the data sources 26, the conversion server 16, a transactionalserver 18, and the control server 20. The processing module 44 furtherstores and retrieves data in the database 30. The processing module 44is discussed in greater detail with respect to FIGS. 2-3 and thedatabase 30 is discussed in greater detail with reference to FIG. 3 .

Each augmentation system 14 includes another plurality of user devices32, another plurality of subscriber devices 34, another portion of thenetwork 28, and an augmentation server 24. The augmentation server 24includes another processing module 44 and another database 30. Each ofthe conversion server 16, the transactional server 18, and the controlserver 20 includes another processing module 44 and another database 30.

Each data source 26 may be implemented utilizing one or more of aserver, a subscription service, a website data feed, or any other portalto data messages 38 that provide utility for operation of thecommunication system 10. Further examples of the data source 26 includesone or more of a financial market server, a census server, a governmentrecord server, another transactional server, another control server,another conversion server, another legacy server, a weather service, ascreen scraping algorithm, a website, another database, a scheduleserver, a live traffic information feed, an information server, aservice provider, and a data aggregator. The data messages 38 includesone or more of live financial market information, historical financialmarket information, weather information, a user daily activity schedule(e.g., a school schedule, a work schedule, a delivery schedule, a publictransportation schedule), real-time traffic conditions, a roadconstruction schedule, a community event schedule, address of residenceinformation, user lifestyle information (e.g., smoker, non-smoker,physical activities, etc.), user death records, mortality tables, andother information associated with a user.

In general, and with respect to the asset reconfiguration andreassignment within the communication system 10, the communicationsystem 10 supports three primary functions. The three primary functionsinclude: 1) determining desired financial attributes of a financialsystem (e.g., supported by an underperforming legacy asset base), 2)facilitating acquisition of an augmenting asset bundle to enhance thefinancial system (e.g., enhancing and/or replacing the legacy assetbase, and 3) facilitating the enhancement of the financial systemutilizing the augmenting asset bundle such that the financial systemsubstantially achieves the desired financial attributes. Thecommunication system may perform one or more of the three primaryfunctions to provide the asset reconfiguration and reassignment.

The financial system is associated with the legacy system 12 where aplurality of users of the user devices 32 and the subscriber devices 34are investors/beneficiaries of the legacy asset base supporting thefinancial system. The plurality of users may include thousands, hundredsof thousands, or even millions of users. The financial system includesany system to derive value for the plurality of users (e.g., balancesheet value and/or cash flow value) from the legacy asset base. Examplesof the financial system includes a money market, a bond fund, a hedgefund, a pension system, and a stock fund. The desired financialattributes include one or more of present and future values of thelegacy asset base, cash flows enabled by the legacy asset base, ongoingcosts associated with the financial system, and return on investmentlevels for the legacy asset base. The legacy asset base may includethousands, hundreds of thousands, or even millions of individual assets,where assets may include tangible hard assets (e.g., property title,precious metals, commodities, etc.) and monetary assets (e.g., bonds,stocks, life insurance policies,

The augmenting asset bundle includes a bundle of selected assetsacquired from one or more of the augmentation systems 14, wherecandidate assets associated with the augmentation systems 14 includesthousands, hundreds of thousands, and even millions of assets. Theassets are selected such that when combined or replacing assets of thelegacy assets, the desired financial attributes of the financial systemcan substantially be reached. The facilitating of the enhancement of thefinancial system utilizing the augmenting asset bundle manipulates(e.g., splits, un-bundles, transforms, re-bundles, retitles, etc.) theselected assets for combination with or the replacement of assets of thelegacy asset base.

The first primary function includes the communication system 10determining desired financial attributes of a financial system. In anexample of operation where the financial system of the legacy system 12is a pension system for over 100,000 pensioners, the legacy asset baseincludes assets that are a combination of cash and bonds, and theaugmentation systems 14 lists millions of available life insurancepolicies, the processing module 44 of the control server 20 determinesto evaluate the financial system. For example, the control server 20receives, via the network 28, a control message 36 from the conversionserver 16, where the control message 36 includes a request to addressunderperformance of the legacy asset base associated with the legacysystem 12. Having determined to evaluate the financial system, thecontrol server 20 characterizes the financial system to produce adesired cash flow and desired valuation improvement or left for thelegacy asset base. For example, the control server 20 receives, via thenetwork 28, another control message 36 from the legacy server 22 thatincludes information associated with the financial system, and evaluatesthe information associated with the financial system to determine thedesired cash flow and desired valuation lift. The first primary functionis discussed in greater detail with reference to FIGS. 5A-5B.

The second primary function includes the communication system 10facilitating acquisition of an augmenting asset bundle to enhance thefinancial system. In an example of operation, the processing module 44of the control server 20 accesses augmenting asset information toextract candidate asset characteristics and down selects candidateassets that compare favorably to augmenting asset preferences. Thecandidate asset characteristics includes one or more of asset identifier(ID), asset type (e.g., stock, bond, life insurance policy, tangibleasset), estimated fair market value (FMV) of the asset, purchase priceof the asset, a risk level associated with the asset, a risk levelassociated with the particular augmentation system tied to the asset,associated liabilities (e.g., premium payments), associated payouts(e.g., a death benefit of an insurance policy), estimated payout timing(e.g., estimated year of a life insurance death benefit payout), anestimated return on investment (ROI) level, and demographics of entitiesassociated with the asset (e.g., age and other characteristics of aninsured person associated with an insurance policy). The augmentingasset preferences includes one or more of a maximum desired risk levelassociated with the asset, a maximum desired risk level associated withthe augmentation system tied to the asset, a maximum liability level, aminimum payout level, a minimum ROI level, and one or more preferreddemographics of the entities associated with the asset. For example, thecontrol server 20 receives control messages 36 from one or more of theaugmentation servers 24, where the control messages 36 includes thecandidate asset characteristics, and receives further control messages36 from the conversion server 16, where the further control messages 36includes the augmenting asset preferences.

Having obtained the candidate asset characteristics and the augmentingasset preferences, the control server 20 searches through availableassets of the one or more augmentation systems 14 to down select thecandidate assets that compare favorably to the augmenting assetpreferences. For example, the control server 20 exchanges controlmessages 36 with the augmentation server of each of the one or moreaugmentation systems 14 to identify each available asset, compares theasset characteristics of the available asset to the augmenting assetpreferences, and identify assets where the comparison is favorable(e.g., estimated ROI greater than minimum desired ROI, estimated risklevel lower than maximum desired risk level, etc.) to produce the downselected candidate assets.

Having identified the down selected candidate assets, the control server20 determines a financial contribution of each of the down selectedcandidate assets. For example, the control server estimates a balancesheet contribution (e.g., a portion of the desired lift) and a cash flowcontribution (e.g., a portion of the desired cash flow) for each downselected candidate asset based on the candidate asset characteristics.The control server 20 may produce the estimates based on the downselected candidate assets in an un-altered form and may produce furtherestimates based on altered forms of the down selected candidate assets,where each of the altered down selected candidate assets arereconfigured. The reconfiguring of a plurality of assets (e.g., selectedcandidate assets) includes the deconstruction of each of the assets intodeconstructed asset elements of two or more element types in accordancewith a deconstruction approach and re-bundling pluralities ofdeconstructed asset elements into two or more new asset bundles inaccordance with a re-bundling approach to substantially satisfied thedesired cash flow and desired valuation lift of the financial system,where each new asset bundle is generally titled to a different entity.For instance, the control server 20 utilizes a default deconstructionapproach and default re-bundling approach to produce financialcontributions of the down selected candidate assets when reconfigured(e.g., deconstructed and re-bundled in accordance with the defaultdeconstruction approach and default re-bundling approach).

Having determined the financial contributions of each of the downselected candidate assets, the control server 20 selects assets from thedown selected candidate assets to produce the augmenting asset bundle.The selecting includes choosing an asset selection approach to make theselections and completing the selecting utilizing the identifiedselection approach. The selection approaches include one or more ofselecting assets that individually produce a highest level of ROI,selecting assets that produce a highest level of cash flow, selectingassets that produce a highest level of lift, selecting assets associatedwith highest levels of favorable financial contributions weighted byrisk (e.g., asset risk, augmenting system risk, and transactional serverentity risk), a random selection approach, and any other approach tooptimize selection of the assets when considering utilization ofdeconstructed elements of the assets. The choosing of the assetselection approach may be based on one or more of a predetermination, arequest, a correlation of historically utilized selection approaches andfinancial results, and a weighting factor that considers multipledesired outcomes.

Having chosen the asset selection approach, the control server 20utilizes the asset selection approach to select assets from the downselected candidate assets based on the financial contributions toproduce the augmenting asset bundle revealing characteristics of theselected assets (e.g., asset ID, asset type, etc.). For example, thecontrol server 20 exchanges further control messages 36 with the one ormore augmentation servers 24 to complete acquisition of the selectedassets of the augmenting asset bundle based on the financialcontributions of the selected assets.

The third primary function includes the communication system 10facilitating the enhancement of the financial system utilizing theaugmenting asset bundle such that the financial system substantiallyachieves the desired financial attributes. In an example of operation,the control server selects a server to perform the reconfiguring of theacquired assets. The selection may be based on one or more of apredetermination, a request, and historical reconfiguring results. Forexample, the control server 20 selects the conversion server 16 toperform the reconfiguring of the acquired assets Having selected theconversion server 16 to perform the reconfiguring of the acquiredassets, the control server 20 facilitates the reconfiguring of theassets of the augmenting asset bundle. The facilitating includesselecting the deconstruction approach, selecting the re-bundlingapproach, and initiating the reconfiguring utilizing the selectedapproaches. The selecting may be based on one or more of apredetermination, a request, information extracted from data messages 38of one or more of the data sources 26 (e.g., current market conditions),and historical financial results based on various approaches. Theinitiating of the reconfiguring includes performing the reconfiguring bythe control server 20 and/or issuing a control message 36 to theconversion server 16, where the control message 36 includes a request toperform the reconfiguring of the assets of the augmenting asset bundlein accordance with the selected deconstruction approach and the selectedre-bundling approach. The control message 36 may further include thecharacteristics of the selected assets of the augmenting asset bundle.For example, the conversion server 16 deconstructs each asset of theaugmenting asset bundle in accordance with the deconstruction approachto produce two or more deconstructed asset elements (e.g., of two ormore element types) and re-bundles pluralities of the deconstructedasset elements in accordance with the re-bundling approach to producethe two or more asset bundles.

Having facilitated the reconfiguring of the assets, the control server20 facilitates the reassignment of the reconfigured assets where the twoor more asset bundles are to be titled to two or more entities of thecommunication system 10 to substantially satisfied the desired cash flowand desired valuation lift of the financial system. The facilitatingincludes issuing titling information to the conversion server 16 suchthat the conversion server 16 titles the two or more asset bundles inaccordance with the titling information. Having received the titlinginformation, the conversion server 16 produces two asset bundles andissues the titling information via a control message 36 to the legacyserver 22 to associate a first asset bundle with the legacy system 12and issues the titling information via another control message 36 to thetransactional server 18 to associate a second asset bundle with thetransactional server 18.

Having facilitated the titling of the two or more asset bundles, thecontrol server 20 identifies the transactional server 18 to facilitatesubsequent financial transactions utilizing the new asset bundlesproduced from the re-bundling of the deconstructed elements of theacquired assets. For example, the control server 20 issues a controlmessage 36, via the network 28, to the transactional server 18, wherethe control message 36 includes subsequent financial transactioninformation (e.g., how to utilize the new asset bundles). For instance,the transactional server 18 exchanges control messages 36 with anaugmentation server 24 associated with a particular asset to settle aperiodic liability (e.g., the transactional server 18 facilitates aliability payment to the augmentation server 24 such as a life insurancepremium payment) and to collect a cash flow (e.g., a life insurancepolicy death benefit payment). As another instance, the transactionalserver 18 partitions the cash flow from the augmentation server 24 intoa first portion and a second portion, where the first portion isassociated with the legacy server 22 (e.g., a portion of the lifeinsurance policy death benefit payment flows to the pension systemassociated with the financial system of the legacy server 22) and thesecond portion is associated with the transactional server 18 (e.g., aholdback if any). Such financial transactions may include one or more ofelectronic money wire transfers and blockchain encoded secure fundstransfer.

In various embodiments, a non-transitory computer readable storagemedium includes at least one memory section that stores operationalinstructions that, when executed by one or more processing modules ofone or more computing devices that each include a processor and amemory, causes each processing module to perform operations includingthe above-described asset reconfiguration and reassignment within thecommunication system.

FIG. 2 is a schematic block diagram of an embodiment of the user device32 and the subscriber device 34 of the communication system 10 thatincludes a computing core 50, a visual output device 74 (e.g., a displayscreen, a light-emitting diode), a user input device 76 (e.g., keypad,keyboard, touchscreen, voice to text, etc.), an audio output device 78(e.g., a speaker, a transducer, a motor), a visual input device 80(e.g., a photocell, a camera), a sensor 82 (e.g., an accelerometer, avelocity detector, electronic compass, a motion detector, electronicgyroscope, a temperature device, a pressure device, an altitude device,a humidity detector, a moisture detector, an image recognition detector,a biometric reader, an infrared detector, a radar detector, anultrasonic detector, a proximity detector, a magnetic field detector, abiological material detector, a radiation detector, a mass and/or weightdetector, a density detector, a chemical detector, a gas detector, asmoke detector, a fluid flow volume detector, a DNA detector, a windspeed detector, a wind direction detector, a medical condition detector,a human activity detector, a motion recognition detector, and a batterylevel detector), one or more universal serial bus (USB) devices 1-U, oneor more peripheral devices, one or more memory devices (e.g., a localmemory, a flash memory device 92, one or more hard drives 94, one ormore solid state (SS) memory devices 96, and/or cloud memory 98), anenergy source 100 (e.g., a battery, a generator, a solar cell, and afuel cell), one or more wireless location modems 84 (e.g., a GPSreceiver, a Wi-Fi transceiver, a Bluetooth transceiver, etc.), one ormore wireless communication modems 86 (e.g., 4G, 5G cellular), a wiredlocal area network (LAN) 88, and a wired wide area network (WAN) 90

The computing core 50 includes a video graphics processing module 52,one or more processing modules 44, a memory controller 56, one or moremain memories 58 (e.g., RAM), one or more input/output (I/O) deviceinterface modules 62 (e.g., interfaces), an input/output (I/O)controller 60, a peripheral interface 64, one or more USB interfacemodules 66, one or more network interface modules 72, one or more memoryinterface modules 70, and/or one or more peripheral device interfacemodules 68. Each of the interface modules 62, 66, 68, 70, and 72includes a combination of hardware (e.g., connectors, wiring, etc.) andoperational instructions stored on memory (e.g., driver software) thatis executed by the processing module 44 and/or a processing circuitwithin the interface module. Each of the interface modules couples toone or more components of the user device 32. For example, one of the TOdevice interface modules 62 couples to an audio output device 78. Asanother example, one of the memory interface modules 70 couples to flashmemory 92 and another one of the memory interface modules 70 couples tocloud memory 98 (e.g., an on-line storage system and/or on-line backupsystem).

The main memory 58 and the one or more memory devices include a computerreadable storage medium that stores operational instructions that areexecuted by one or more processing modules 44 of one or more computingdevices (e.g., the user device 32) causing the one or more computingdevices to perform functions of the communication system 10. Forexample, the processing module 44 retrieves the stored operationalinstructions from the HD memory 94 for execution.

FIG. 3 is a schematic block diagram of an embodiment of the servers16-24 of the communication system 10 that includes a computing core 110and elements of the user device 32 (e.g., FIG. 2 ), including one ormore of the visual output device 74, the user input device 76, the audiooutput device 78, the memories 92-98 to provide the database 30 of FIG.1 , the wired LAN 88, and the wired WAN 90. The computing core 110includes elements of the computing core 50 of FIG. 2 , including thevideo graphics module 52, the plurality of processing modules 44, thememory controller 56, the plurality of main memories 58, theinput-output controller 60, the input-output device interface module 62,the peripheral interface 64, the memory interface module 70, and thenetwork interface modules 72.

FIGS. 4A-4B are schematic block diagrams of another embodiment of acommunication system that includes the legacy server 22 of FIG. 1 , theconversion servers 16 of FIG. 1 , the transactional server 18 of FIG. 1, the augmentation server 24 of FIG. 1 , and the control server 20 ofFIG. 1 . The control server 20 includes the processing module 44 of FIG.1 and the database 30 of FIG. 1 . The processing module 44 includes adiagnostic module 120, an acquisition module 122, and an augmentationmodule 124. Each of the diagnostic module 120, the acquisition module122, and the augmentation module 124, may be implemented utilizing aprocessing module. The communication system functions to facilitateasset reconfiguration and reassignment.

FIG. 4A illustrates an example of the facilitating of the assetreconfiguration and reassignment where the legacy server 22 communicatesfinancial system information 130 to the conversion servers 16. Thefinancial system information 130 includes one or more of yieldcharacteristics (e.g., ROI, timing of yields) of the legacy asset baseof the financial system associated with the legacy server 22, a currentvaluation of the legacy asset base, a risk level associated with thelegacy asset base, a liability schedule (e.g., a pension liabilityschedule when the financial system is a pension system), anddemographics associated with users of the financial system (e.g., ages,lifestyles associated with pension participants).

Having received the financial system information 130, the conversionservers 16 forwards the financial system information 130 to thediagnostic module 120. The diagnostic module 120 determines desiredfinancial attributes 132 for the financial system supported by thelegacy asset base by analyzing the financial system information 130 inaccordance with historical financial system information and/or currentmarket conditions. The desired financial attributes 132 includes one ormore of a desired cash flow level and timing, and a desired valuationlift such that the valuation of the legacy asset base is corrected to adesired legacy asset value when the legacy asset base is augmented inthe following step. The operation of the diagnostic module 120 isdiscussed in greater detail with reference to FIGS. 5A-5B.

The acquisition module 122 facilitates acquisition of an augmentingasset bundle to enhance the legacy asset base such that the desiredlegacy asset value can be obtained while meeting the desired cash flowlevels and timing. For example, the acquisition module 122 analyzescandidate asset characteristics of augmenting asset information 134received from the augmentation server 24 to screen for candidate assetsfor acquisition, evaluates a financial contribution for each of thepotentially acquired assets, selects a combination assets that whenaggregated have a total financial contribution that compares favorablyto the desired cash flow and desired valuation lift, and facilitatesacquisition of the selected assets to produce acquired augmenting assetbundle information 136 (e.g., includes characteristics of the selectedassets as well as identification). The operation of the acquisitionmodule 122 is discussed in greater detail with reference to FIGS. 6A-6C.

The augmentation module 124 facilitates enhancement of the legacy assetbase with the augmenting asset bundle to enable the financial system inaccordance with the desired financial attributes (e.g., cash flow andvaluation lift). The facilitation includes the augmentation module 124performing enhancement or the augmentation module 124 instructinganother server (e.g., the conversion servers 16) to perform theenhancement. The enhancement includes selecting an asset deconstructionapproach and utilizing the selected asset deconstruction approach, whereeach asset of the acquired augmenting asset bundle is deconstructed toproduce at least two deconstructed elements and where individualelements are re-bundled into two or more groupings for titling to two ormore entities of the communication system. For example, deconstructedelements are re-bundled into a first grouping that is to be titled tothe legacy server 22 to replace the legacy asset base such that the newvaluation and expected cash flow associated with the first groupingmeets or exceeds the desired cash flow and desired valuation lift andother deconstructed elements are re-bundled into a second grouping thatis to be titled to the transactional server 18. For instance, theaugmentation module 124 outputs asset augmentation information 138 tothe merchant server 16, where the asset augmentation informationincludes the selected asset deconstruction approach, and new assettitling information. Having received the asset augmentation information138, the conversion servers 16 issues asset and liability partitioninginformation 140 to the legacy server 22 and to the transactional server18, where the asset liability partitioning information 140 includesasset deconstruction results (e.g., characteristics of the deconstructedelements) and deconstructed asset element title information (e.g., whichdeconstructed elements are now affiliated with which entity). Theoperation of the augmentation module 124 is discussed in greater detailwith reference to FIGS. 7A-7C.

FIG. 4B further illustrates the example of the facilitating of the assetreconfiguration and reassignment where the transactional server 18, whenreceiving the asset and liability partitioning information 140, issuesliability settlement information 142 to the augmentation server 24 whendetecting that a liability is to be resolved (e.g., making a lifeinsurance policy premium payment in accordance with a schedule), issuesfurther liability settlement information 142 to the augmentation server24 when detecting that an asset settlement is to be resolved (e.g.,submitting a death benefit claim for a particular life insurance policybased on detecting death of the insured), and receiving asset settlementinformation 144 from the augmentation server 24 to complete settlementof a particular asset (e.g., receiving a payment transaction for a deathbenefit related to a life insurance policy).

Having received asset settlement information 144, the transactionalserver 18 partitions a payment associated with the received assetsettlement information 144 into two or more payment partitions, wherethe partitioning is in accordance with the asset and liabilitypartitioning information 140. For example, the transactional server 18partitions the payment into X and Y portions, where the X portion isassociated with the legacy server 22 in accordance with titlinginformation of the asset and liability partitioning information 140,where the Y portion is associated with the transactional server 18 inaccordance with the titling information of the asset and liabilitypartitioning information 140, and where X+Y=100%.

Having partitioned the payment, the transactional server 18 issuessub-asset settlement information 146 to the legacy server, where thesub-asset settlement information 146 facilitates a payment transaction(e.g., bank wire, electronic transaction, E-cash, blockchain currency)for a portion of the payment (e.g., a portion of the payment transactionfor the death benefit related to the life insurance policy to beassigned to the legacy server 22). Having received the sub-assetsettlement information 146, the legacy server 22 issues financial systemoutput information 148 to include a desired cash flow in accordance withthe financial system funded by a plurality of such payment transactionsas communicated by the sub-asset settlement information 146. Forexample, the legacy server 22 facilitates payment transactions tosatisfy periodic payments to pension plan participants funded by theportion of the death benefit payments, when the financial system is apension system and the acquired assets of the augmentation server 24include life insurance policies that have been deconstructed andre-bundled.

FIG. 4C is a logic diagram of an example of a method of enhancing alegacy asset base that includes step 160 where a processing module(e.g., of a communication system) determines desired financialattributes of a financial system supported by a legacy asset base. Forexample, the processing module determines to evaluate the financialsystem (e.g., by request, in accordance with a schedule, when a metricof the financial system is detected to be unfavorable compared to adesired value), analyzes the financial system to produce a desired cashflow level (e.g., identifies a stream of liability payments), andanalyzes the financial system to produce a desired valuation lift (e.g.,identifies a gap between a current valuation of the legacy asset baseand a desired valuation of the legacy asset base).

The method continues at step 162 where the processing module facilitatesacquisition of an augmenting asset bundle to enhance the legacy assetbase. For example, the processing module identifies augmenting assetpreferences (e.g., receives, performs a lookup, interprets a queryresponse), accesses augmenting asset information from an augmentingasset entity (e.g., an augmentation server) to extract candidate assetcharacteristics (e.g., searches through thousands of life insurancepolicy records), down selects candidate assets the compare favorably tothe augmenting asset preferences (e.g., a favorable quality level),determines financial contributions of each of the down selectedcandidate assets (e.g., when split utilizing a deconstruction approach),selects an asset selection approach (e.g., to maximize one or more ofcash flow contribution and balance sheet contribution), completeselection and acquisition from the down selected candidate assets toproduce the augmenting asset bundle utilizing the selected assetselection approach where an estimated financial contribution of theaugmenting asset bundle compares favorably to the desired cash flow andvaluation left, and summarize the augmenting asset bundle to revealselected asset characteristics.

The method continues at step 164 where the processing module facilitatesenhancement of the legacy asset base with the augmenting asset bundle toenable the financial system in accordance with the desired financialattributes. For example, the processing module identifies a custodialentity and associated custodial server (e.g., a transactional serveridentified in a predetermination or contest), selects a deconstructionapproach for the acquired augmenting asset bundle where an estimatedvalue of deconstructed asset elements compares favorably to one or moreof the desired cash flow, the desired valuation lift, and other fundingrequirements (e.g., value to be generated associated with the custodialserver, generates title transfer information for the deconstructed assetelements, and facilitates the construction of the acquired augmentingasset bundle utilizing the deconstruction approach to produce thedeconstructed asset elements (e.g., deconstruct or request that anotherentity such as the custodial server perform the deconstruction byissuing a request that includes selected asset title transferinformation and the selected asset deconstruction approach).

The processing module may determine the estimated value of thedeconstructed asset elements by calculating the fair market or presentvalue of a first deconstructed element (e.g., a death benefit of a lifeinsurance policy) of the deconstructed asset as a function of: the valueof a corresponding second deconstructed element (e.g., a series ofpremium payments associated with the life insurance policy) of thedeconstructed asset, a credit rating associated with the custodialentity (e.g., likelihood of the custodial entity continuing to make lifeinsurance premium payments to a corresponding leverage is comedy), acredit rating associated with the augmenting asset entity (e.g.,likelihood that life insurance company associated with the lifeinsurance policy will make the death benefit payment), and a lifeexpectancy of an insured entity (e.g., a person) associated withinsurance policy. The calculation of the value may further be based onmarket conditions where a plurality of augmenting assets aredeconstructed and re-bundled by others thus influencing a general marketcondition for valuations and spreads due to arbitrage as suchdeconstructed elements pass through multiple levels of ownership andretitling.

FIG. 4D is a logic diagram of another method of enhancing a legacy assetbase within a computing system and/or communication system. Inparticular, a method is presented for use in conjunction with one ormore functions and features described in conjunction with FIGS. 1-3, 4A,4B, 4C, and also FIG. 4D. The method includes step 150 where aprocessing module of one or more processing modules of one or morecomputing devices of the computing system determines desired financialattributes of a legacy financial system, where the legacy financialsystem is supported by a legacy asset base, where the legacy asset baseincludes a plurality of legacy assets associated with a plurality oflegacy asset types, and where the plurality of legacy assets is toprovide favorable support for a plurality of ongoing financialobligations in accordance with the desired financial attributes.

The determining the desired financial attributes includes one or more ofestablishing a desired valuation lift of the legacy asset base inaccordance with a difference between a desired valuation of the legacyasset base and a current valuation of the legacy asset base when thedesired valuation of the legacy asset base is greater than the currentvaluation of the legacy asset base, identifying, for at least oneunfavorably-performing legacy asset of the plurality of legacy assets,an associated level of desired support for the plurality of ongoingfinancial obligations, analyzing a level of favorable support for theplurality of ongoing financial obligations to produce the desiredfinancial attributes and interpreting an input to produce the desiredfinancial attributes.

The method continues at step 152 where the processing module selects, inaccordance with the desired financial attributes, a subset of augmentingassets from a plurality of available augmenting assets to produce anaugmenting asset bundle, where each available augmenting asset isassociated with a future time-estimated benefit payment and a series oftime-certain obligated payments. The selecting of the subset ofaugmenting assets may be accomplished by a variety of approaches.

A first approach of selecting of the subset of augmenting assetsincludes determining, for each augmenting asset of the plurality ofavailable augmenting assets, a valuation difference, wherein thevaluation difference is a difference between a fair market value and anet present value, ranking the plurality of available augmenting assetsbased on the valuation difference associated with each augmenting assetto produce a rank ordered list of available augmenting assets, andselecting the subset of augmenting assets based on the rank ordered listof available augmenting assets, where financial aspects of the subset ofaugmenting assets compares favorably to the desired financialattributes.

The selecting of the subset of augmenting assets based on the rankordered list further includes one or more of analyzing the rank orderedlist to identify available augmenting assets associated with a greatestlevel of valuation difference, analyzing the rank ordered list toidentify available augmenting assets associated with a maximum desiredlevel of fair market value, analyzing the rank ordered list to identifyavailable augmenting assets associated with a minimum desired level ofnet present value, selecting a number of available augmenting assetssuch that a sum of the fair market values of the selected availableaugmenting assets compares favorably to a desired valuation lift of thelegacy asset base, and selecting another number of available augmentingassets such that a sum of the net present values of the selectedavailable augmenting assets compares favorably to a desired maximumaggregate net present value.

A second approach of selecting of the subset of augmenting assetsincludes one or more of identifying the subset of augmenting assetsassociated with favorable support of a desired cash flow level for theongoing financial obligations, identifying the subset of augmentingassets associated with a desired timing of the desired cash flow levelfor the ongoing financial obligations, identifying the subset ofaugmenting assets associated with a desired valuation of the legacyasset base, identifying the subset of augmenting assets associated witha desired minimum rate of return for the augmenting asset bundle, andidentifying the subset of augmenting assets associated with a desiredmaximum risk level for the augmenting asset bundle.

The method continues at step 154 where the processing module determines,in accordance with the desired financial attributes, a first portion ofan aggregate of the future time-estimated benefit payments of theaugmenting asset bundle for assignment to the legacy asset base. Thedetermining the first portion of the aggregate of the futuretime-estimated benefit payments of the augmenting asset bundle includesone or more of selecting a number of augmenting assets of the augmentingasset bundle such that a sum of fair market values of the selectedaugmenting assets compares favorably to a desired valuation lift of thelegacy asset base, and selecting the number of augmenting assets of theaugmenting asset bundle such that such that a sum of fair market valuesof each remaining augmenting asset of remaining augmenting assetscompares favorably to a sum of an aggregate of each of the series oftime-certain obligated payments associated with the augmenting assetbundle.

The method continues at step 156 where the processing module assigns aremaining portion of the aggregate of the future time-estimated benefitpayments of the augmenting asset bundle to another entity. For example,the processing module facilitates titling of the remaining portion to apension plan sponsor associated with a pension plan that is affiliatedwith the legacy asset base. As another example, the processing modulefacilitates titling of the remaining portion to a financial custodian.

The method continues at step 158 where the processing module assigns anaggregate of each of the series of time-certain obligated payments ofthe augmenting asset bundle to the other entity. For example, theprocessing module establishes a commitment from the financial custodianto fund the aggregate of each of the series of time-certain obligatedpayments when the financial custodian receives the remaining portion ofthe aggregate of the future time-estimated benefit payments, where thebenefit payments and the obligated payments are similar in values.

The method continues at step 166 for the processing module detectsavailability of a first future time-estimated benefit payment of thefirst portion of the aggregate of the future time-estimated benefitpayments (e.g., a life settlement payment is available). The methodcontinues at step 168 where the processing module facilitates a paymenttransaction of the first future time-estimated benefit payment from anassociated payer to the legacy asset base. For example, the processingmodule issues a payment request to a financial server of the associatedpayer (e.g., a life insurance company) such that payment is made fromthe associated payer to the legacy asset base (e.g., to a pension plan).

The method described above in conjunction with the processing module canalternatively be performed by other modules of the communication system10 of FIG. 1 or by other devices. In addition, at least one memorysection (e.g., a computer readable memory, a non-transitory computerreadable storage medium, a non-transitory computer readable memoryorganized into a first memory element, a second memory element, a thirdmemory element, a fourth element section, a fifth memory element etc.)that stores operational instructions can, when executed by one or moreprocessing modules of one or more computing devices (e.g., one or moreservers, one or more user devices) of the communication system 10, causethe one or more computing devices to perform any or all of the methodsteps described above.

FIG. 5A is a schematic block diagram of an embodiment of a diagnosticmodule that includes an activation module 170, a characterization module172, a cash flow module 174, and a lift module 176, where the diagnosticmodule 120 communicates with one or more of the conversion server 16 ofFIG. 1 , the data source 26 of FIG. 1 , and the transactional server 18of FIG. 1 . Each of the activation module 170, the characterizationmodule 172, the cash flow module 174, and the lift module 176, may beimplemented utilizing a processing module.

In an example of operation of the diagnostic module, the activationmodule 170 selects a financial system valuation trigger approach from aplurality of evaluation trigger approaches. The plurality of evaluationtrigger approaches includes one or more of a legacy asset base valuebelow a low threshold level, a desired cash flow level above a highthreshold level, a desired valuation lift above a high threshold level,and evaluation time frame has expired, receiving a request, anddetecting that an external factor level is beyond a normal thresholdlevel. The selecting includes one or more of utilizing apredetermination, interpreting a request, and interpreting a receivedalert from the server or data source (e.g., receive a control message 36and/or data message 38 from one or more of the conversion server 16, thedata source 26, and the transactional server 18).

Having selected the evaluation trigger approach, the activation module170 indicates to evaluate a financial system associated with theconversion server 16 when detecting a trigger threshold event inaccordance with the evaluation trigger approach (e.g., where theconversion server 16 is affiliated with a sponsor that is associatedwith the financial system of a legacy server).

When evaluating the financial system, the characterization module 172identifies financial system desired yield characteristics 180. Thefinancial system desired yield characteristics includes one or more ofan ROI level, a dividend level or similar payout level, and payouttiming, (e.g., for payouts for a pension liability schedule, pensionparticipant demographics, pension participant mortality information,pension participant lifestyle information). The identifying includes oneor more of receiving, performing a lookup, interpreting a queryresponse, interpreting financial system information 130 received fromthe conversion server, and generating an estimate based on a last storedfinancial system information.

The characterization module 172 determines legacy asset basecharacteristics 184 based on the financial system information 130. Thelegacy asset base characteristics include one or more of, for each assettype, a face amount, a fair market value, a net present value,associated timing, and a risk level. The determining includes one ormore of interpreting a query response, performing a lookup, interpretinga data message 38 from the data source 26, and interpreting thefinancial system information 130 from the conversion server 16.

Having generated the desired yield characteristics 180 and the legacyasset base characteristics 184, the characterization module 172 sendsthe desired yield characteristics 180 to the cash flow module 174 andsends the legacy asset base characteristics 184 to the lift module 176.The cash flow module 174 determines a desired cash flow 182 based on thefinancial system desired yield characteristics 180 (e.g., cash flow tosubstantially match desired pension payouts when the financial system isa pension system). The lift module 176 determines a value of the legacyasset base based on the legacy asset base characteristics 184. Thedetermining includes one or more of calculating utilizing at least oneof fair market value approach, a net present value approach, andinterpreting a query response (e.g., issue a value request to thetransactional server 18, where the transactional server 18 utilizesmarket values to generate an estimate). The lift module determines avalue of the desired cash flow based on the desired cash flow 182. Thedetermining includes one or more of calculating utilizing at least oneof a fire market value approach, a net present value approach, andinterpreting a query response (e.g., issue a value request to theconversion server 16 and receive the query response). The lift modulecalculates a difference between the value of the desired cash flow andthe value of the legacy asset base to produce a desired valuation lift.The lift module outputs desired financial attributes 132 to include thevalue of the desired cash flow and the desired valuation lift.

FIG. 5B is a logic diagram of an example of a method of diagnosing alegacy asset base which includes step 190 where an activation moduleselects an evaluation trigger approach. The selecting may be based onone or more of utilizing a predetermination, interpreting a request, andreceiving an alert. The method continues at step 192 where theactivation module indicates to evaluate when detecting a triggerthreshold event in accordance with the evaluation trigger approach. Forexample, the activation module detects a favorable comparison of aninput to a corresponding condition of the evaluation trigger approachand indicates to evaluate.

The method continues at step 194 where a characterization moduleidentifies financial system desired yield characteristics. Theidentifying includes one or more of interpreting a query response,performing a lookup, and receiving financial system information thatincludes the financial system desired yield characteristics. The methodcontinues at step 196 where the characterization module determineslegacy asset base characteristics. The determining includes one or moreof interpreting a message in response to a query, performing a lookup,and interpreting a data message from a data source.

The method continues at step 198 where a cash flow module determinesdesired cash flow. The determining may be based on calculating thedesired cash flow based on the desired yield characteristics. The methodcontinues at step 200 where a lift module determines a value of thelegacy asset base based on the legacy asset base characteristics. Thedetermining includes utilizing at least one of fair market valueapproach, a net present value approach, and interpreting market and/orhistorical conditions. The method continues at step 202 where the liftmodule determines a value of desired cash flow. The determining includesutilizing at least one of the fair market value approach, the netpresent value approach, and interpreting market and/or historicalconditions. The method continues at step 204 where the lift modulecalculates a difference (e.g. subtract) between the value of desiredcash flow and the value of the legacy asset base to produce a valuationlift.

FIG. 6A is a schematic block diagram of an embodiment of an acquisitionmodule that includes a screening module 210, a selection module 212, anda trading module 214, where the acquisition module 122 communicates withone or more of the augmentation server 24 of FIG. 1 , and the datasource 26 of FIG. 1 . Each of the screening module 210, the selectionmodule 212, and the trading module 214, may be implemented utilizing aprocessing module.

In an example of operation of the acquisition module 122, a screeningmodule 210 identifies augmenting asset preferences by interpretingaugmenting asset information 134 from the augmentation server 24 and thedesired financial attributes 132. The augmenting asset preferencesincludes one or more of a risk level of an entity associated with theaugmentation server, a credit rating of the entity, the validity ofavailable assets (e.g., insurable interest, title chain), and anestimated asset ROI.

Having identified the augmenting asset preferences, the screen module210 identifies candidate assets that are associated with attributes thatcompare favorably to the augmenting asset preferences to produce downselected candidate asset information 220. For example, the selectionmodule 212 interprets the augmenting asset information 134 to identifycharacteristics of the candidate assets, compares the characteristics tothe asset preferences, and indicates the down selection (e.g.,identifiers of selected assets) when the attributes of the candidateasset compares favorably to the asset preferences.

The selection module 212 estimates a financial contribution of each ofthe down selected candidate assets, where the estimation is based onvaluation after the asset has been deconstructed. The estimating may bebased on one or more of purchase price from the augmentation server 24,fair market valuation (e.g., based on a data message 38 from the datasource 26 with regards to market pricing), asset and liabilitycomponents of the asset, and matching to the desired financialattributes over a time frame of cash flow (e.g., of death benefitpayments when the asset is a life insurance policy).

Having produced the estimated financial contributions, the selectionmodule 212 chooses an asset selection approach. The asset selectionapproaches include 1) a passive approach where an estimated value afterdeconstructing each asset into a positive asset and a liability, wherethe positive asset is associated with the financial system of the legacyasset based, 2) an active approach where the desired financialattributes are matched to the estimated value after deconstructing eachasset to produce positive assets associated with the financial system,and 3) an iterative approach where each asset is selected one by one tooptimize resulting assets of the financial system in accordance with thedesired financial attributes. The choosing may include one or more ofutilizing a predetermination, interpreting a request, and interpretinghistorical selection data with regards to selection approach andfinancial results.

Having chosen the asset selection approach, the selection module 212completes the selection from the down selected candidate assets toproduce chosen augmenting asset bundle information 222 (e.g., identifiedassets), where the selection is made in accordance with the chosen assetselection approach, and where estimated financial contributions of theaugmenting asset bundle compares favorably to the desired cash flow anddesired valuation lift of the desired financial attributes 132. Thetrading module facilitates acquisition (e.g., purchase) of the assets ofthe augmenting asset bundle to produce acquired augmenting asset bundleinformation 136 that includes selected asset characteristics. Theselected asset characteristics include one or more of identification ofeach asset, title information, expected financial contribution, risklevels, identity of the entity associated with the augmentation serverof the ad set, and the suggested deconstruction approach. Thefacilitating includes exchanging trading information 224 with theaugmentation server 24 to confirm purchase pricing, pass-through offunding in accordance with the purchase pricing, and confirming receiptand title of the purchased assets. Such a financial transaction may becarried out by utilizing one or more electronic financial transactionapproaches including electronic cash, wire transfer, electronic fundstransfer, and a blockchain approach.

FIG. 6B is a diagram of an example of acquiring augmenting assets wherevalues of a plurality of assets are considered based on theircharacteristics and an asset deconstruction approach. The plurality ofassets are associated with augmenting asset information 134. Forexample, a plurality of N augmenting assets, that are available forpurchase (e.g., from an insurance company, from a hedge fund entity,from any other entity) are represented by a plurality of digital recordsindicating augmenting asset information. For example, a digital recordof an asset 8 represents a life insurance policy that is associated withan obligation of a series of premium payments in accordance withobligation requirements to maintain the life insurance policy and aone-time death benefit payment upon death of a person associated with alife insurance policy. An obligation provider provides the obligation(e.g., a series of premium payments on a timely basis) to an obligationrecipient in accordance with the obligation requirements. A risk levelassociated with fulfilling continued payment of the premium payments maybe higher when responsibility for the obligation to make the premiumpayments is associated with an original contingency entity (e.g., aoriginally insured person associated with a life insurance policy) ascompared to when the responsibility for the obligation to make thepremium payments is shifted during a splitting or riving process suchthat the obligation is now associated with another obligation provider(e.g., a financial market entity known for making commitments and in anembodiment committing to make the premium payments with a lower risklevel than the originally insured). A risk level associated withreceiving the one-time death benefit payment may be higher when theassociated life insurance company has an unfavorable death benefitpayment history as compared to other life insurance companies or whenthe risk level of making the premium payments is higher than average.

The valuation of the asset based on the deconstruction approach involvesdeconstructing each asset into two or more deconstructed elements whichmay henceforth be alternatively referred to as deconstructives. Forexample, the asset 8 is deconstructed into an asset deconstructionelement 8 and a liability deconstruction element 8, where the assetdeconstruction element 8 is associated with the death benefit payment inthe life insurance policy example and the liability deconstructionelement 8 is associated with the plurality of premium payments. Theselection of candidate assets to produce down selected candidate assetinformation 220 includes identifying assets associated with assetdeconstruction elements with favorable payouts and payout timing withina desired risk level (e.g., relative to other assets, relative tominimum levels as compared to historical asset element information), andliability deconstruction elements associated with favorable premiumpayments and premium payment timing when under custodial care of anentity with a favorable risk level (e.g., relative to other liabilities,relative to historical liability element information).

In an example of operation to identify digital records of assets forselection and splitting to generate unexpected value due to reassignmentof the obligation to make an obligation (e.g., premium payments), acomputing device analyzes a multitude of available longevity-contingentassets (e.g., augmenting assets information 134 for life insurancepolicies or similar) for purchase to identify a set of candidate assetssuch that each candidate asset of the set of candidate assets has apurchase price that is less than a sum of a net present value of afuture time-estimated benefit payment of the candidate asset and a netpresent value of a series of time-certain obligated payments of thecandidate asset when the candidate asset is split after purchase toreassign the future time-estimated benefit payment to a benefit entityand to reassign the series of time-certain obligated payments to acommon entity. Each available longevity-contingent asset of themultitude of available longevity-contingent assets assigns the futuretime-estimated benefit payment of the available longevity-contingentasset and the series of time-certain obligated payments of the availablelongevity-contingent asset to a common entity associated with theavailable longevity-contingent asset. The analyzing of the multitude ofavailable longevity-contingent assets includes at least one of a varietyof sub-approaches.

A first sub-approach includes determining that the net present value ofthe future time-estimated benefit payment of the candidate asset isgreater upon the split after purchase to reassign the futuretime-estimated benefit payment from the common entity to the benefitentity. A second sub-approach includes determining that the net presentvalue of the series of time-certain obligated payments of the candidateasset is greater upon the split after purchase to reassign the series oftime-certain obligated payments from the common entity to the sponsorentity.

The example method further includes the computing device selecting, inaccordance with a longevity-contingent asset de-construction approach, asubset of available longevity-contingent assets from the set ofcandidate assets to produce selected longevity-contingent assets. Theselected longevity-contingent assets is associated with a fair marketvalue for purchase (e.g., purchase price established by a seller).

The example method further includes the computing device splitting eachof the selected longevity-contingent assets to produce the plurality oflongevity-contingent assets by a series of sub-steps. A first sub-stepincludes reassigning the future time-estimated benefit payment of eachselected longevity-contingent asset from the common entity of theselected longevity-contingent asset to the benefit entity. An aggregateof the future time-estimated benefit payment of each selectedlongevity-contingent asset is associated with an incremental benefit netpresent value.

A second sub-step includes assigning the series of time-certainobligated payments of each selected longevity-contingent asset from thecommon entity of the selected longevity-contingent asset to the sponsorentity to produce a plurality of periodic premium payments for theselected longevity-contingent assets, such that an unexpected beneficialvaluation elevation is created where a sum of the incremental benefitnet present value and an incremental liability net present value isgreater than the fair market value of the selected longevity-contingentassets, so that improved support is provided for an obligation of thesponsor entity for the series of time-certain obligated payments of eachselected longevity-contingent asset of the plurality oflongevity-contingent assets due to the beneficial valuation elevationover direct utilization of the selected longevity-contingent assets. Anaggregate of each series of time-certain obligated payments of eachselected longevity-contingent asset is associated with the incrementalliability net present value.

The example method further includes the computing entity causing arecord set for the plurality of longevity-contingent assets to be storedin a database of a transactional computing device. The transactionalcomputing device is distinct from the computing device. Each recordcorresponds to one of the plurality of longevity-contingent assets andis indexed in the database by an asset identifier of the correspondingone of the plurality of longevity-contingent assets. Each recordincludes the longevity-contingent asset de-construction approach and theasset identifier of the corresponding one of the plurality oflongevity-contingent assets.

The example method of operation further includes the transactionalcomputing device identifying, using the record set for the plurality oflongevity-contingent assets stored in the database of the transactionalcomputing device, a payout of one or more longevity-contingent assets ofthe plurality of longevity-contingent assets. A benefit cash account isutilized to accrue a portion of the payout on behalf of one or morebenefactors. A premium cash escrow is utilized to fund an aggregatedpayment of the plurality of periodic premium payments on behalf of oneor more debtors.

The example method of operation further includes the transactionalcomputing device determining a first portion of the payout to associatewith the premium cash escrow in accordance with the longevity-contingentasset de-construction approach. The example method of operation furtherincludes the transactional computing device determining a second portionof the payout to associate with the benefit cash account based on thefirst portion of the payout and in accordance with thelongevity-contingent asset de-construction approach.

FIG. 6C is a logic diagram of an example of a method acquiringaugmenting assets that includes step 230 where a screening moduleidentifies augmenting asset preferences. For example, the screeningmodule interprets augmenting asset information and desired financialattributes to produce the augmenting asset preferences. The methodcontinues at step 232 where the screening module identifies candidateassets that compare favorably to the augmenting asset preferences toproduce down selected candidate assets. For example, the screen moduleinterprets the augmenting asset information to identify characteristicsof the candidate assets, compares the candidate assets to the assetpreferences, and indicates down selection when the candidate assetcompares favorably to the asset preferences.

The method continues at step 234 where a selection module estimates afinancial contribution of each of the down selected candidate assets,where the asset is to be deconstructed. For example, the selectionmodule analyzes deconstruction of the candidate asset into aninter-related asset and a liability, further based on one or more ofprice, fair market value, and matching to the desired financialattributes were a varying range of timing of benefits of the asset whenthe asset produces benefits (e.g., a death benefit payment of a lifeinsurance policy). The method continues at step 236 where the selectionmodule chooses an asset selection process. The choosing may be based onone or more of a predetermination, interpreting a request, andinterpreting historical selection data and associated financial results.

The method continues at step 238 where the selection module completesselection from the down selected candidate assets to produce chosenaugmenting asset bundle information, where the selection is made inaccordance with the chosen asset selection approach, and where estimatedfinancial contributions of the augmenting asset bundle comparesfavorably to a desired cash flow and a desired valuation lift of thedesired financial attributes. The method continues at step 240 where atrading module facilitates acquisition of the assets of the augmentingasset bundle to produce acquired augmenting asset bundle information.For example, the trading module exchanges trading information with anaugmentation server to confirm purchase pricing, passes through afunding transaction in accordance with the purchase pricing to purchasethe assets, and confirms receipt and title of the purchase of the assetsof the acquired augmenting asset bundle.

FIG. 7A is a schematic block diagram of an embodiment of an augmentationmodule 124 that includes a deconstruction approach module 250 and adeconstruction module 252, where the augmentation module 124communicates with the data source 26 of FIG. 1 and the conversion server16 of FIG. 1 . Each of the deconstruction approach module 250 and thedeconstruction module 252 may be implemented utilizing a processingmodule.

In an example of operation of the augmentation module 124, thedeconstruction approach module 250 identifies a transactional serverassociated with a custodial entity to facilitate ongoing transactions ofa financial system when augmented by an acquired augmenting assetbundle. The identifying includes one or more of interpreting a request,interpreting a query response, declaring a competition winner (e.g., abid), analyzing historical transaction information, identifying adesired risk level for an entity associated with a transactional server,and interpreting risk information associated with entities oftransactional servers.

Having identified the transactional server, the deconstruction approachmodule 250 selects a deconstruction approach for the acquired augmentingasset bundle based on acquired augmenting asset bundle information 136to produce asset deconstruction approach information 260, where anestimated value of deconstructed asset elements compares favorably toone or more of a desired cash flow and a desired valuation lift andother funding requirements (e.g., value to be generated associated withthe transactional server). The deconstruction approaches include a firstapproach where each asset is converted into a first deconstructed assetelement that is an asset and a second peak constructed asset elementthat is a liability, a number of first elements are titled with anentity associated with a legacy server and a remaining number of firstelements with another entity associated with the identifiedtransactional server, substantially all of the second elements aretitled to the entity associated with the identified transactionalserver, where the quantities of tight of the elements is in accordancewith one or more of a net present value, exchange or market valuehistorical pricing, instructed pricing, risk levels of each of theentities, and arbitrage information of a data message 38 received fromthe data source 26.

The deconstruction approaches includes a second approach where incombination with the first approach, a portion of the elements aretitled to an entity associated with the conversion server. The selectingmay be based on one or more of a predetermination, interpreting arequest, interpreting historical results associated with particulardeconstruction approaches, interpreting data messages 38 from the datasource 26 associated with current market conditions, and optimizing alevel of fit for cash flow and for value for at least a portion of theassets for two or more of the deconstruction approaches to identify apresently superior deconstruction approach, where asset elementvaluation depends on risk associated with entities affiliated with oneor more of the legacy server, the transactional server and augmentationserver, the conversion server 16. The selecting further includesoutputting the asset deconstruction approach information to include oneor more of the approach for each asset, a number of assets, identifiersof the assets, and preliminary asset titling information (e.g., whichdeconstructed asset is assigned to which entity).

Having selected the deconstruction approach for each asset, thedeconstruction module 252 facilitates deconstruction of substantiallyeach asset of the acquired augmenting asset bundle utilizing theselected deconstruction approach to produce asset augmentationinformation 138 (e.g., selected asset title transfer information,selected asset deconstruction approaches). The facilitating includesperforming the deconstruction or requesting that the conversion server16 execute the deconstruction (e.g., in accordance with an agreement).

FIG. 7B is a diagram of an example of utilizing augmenting assets whereassets described by acquired augmenting asset bundle information 136 aredeconstructed entitled to produce two or more groupings of deconstructedelements from the assets of an acquired augmenting asset bundle. Forexample, assets 2, 8, and 12 are deconstructed in accordance with adeconstruction approach to produce asset deconstruction elements andliability deconstruction elements, when the assets 2, 8, and 12 are partof the acquired augmenting asset bundle.

Having deconstructed each element, individual elements are partitionedinto two or more groupings, where each grouping is title to a differententity of two or more entities, and where a valuation of each groupingmeets valuation requirements for the groupings and as a whole for thefinancial system of a legacy asset base for augmentation. For example,the value of a title 1 grouping may be driven by the assetdeconstruction elements of the assets 2, 8, and 12 while the value of atitle 2 grouping may be driven by the liability deconstruction elementsof assets 2, 8, 12, and others, along with a cash asset and one or moreasset deconstruction elements from other assets of the acquiredaugmenting asset bundle. Alternatively, the title 1 grouping may includeanother cash asset, or any other asset including bonds etc., and/or oneor more liability deconstructed elements. Further alternatively, thetitle 2 grouping may include shortened liability deconstructed elements,where the shortened liability deconstructed element includes a subset ofa plurality of liability (e.g., payment) cash flows (e.g., 2 of n lifeinsurance policy premium payments, a maximum of 10 years of lifeinsurance premium payments, 75% of each remaining life insurance policypremium payment, etc.).

To predict valuations, the value of the title 1 grouping is a functionof the aggregated value of each asset deconstruction element, where eachasset deconstruction element has a value that's a function of acorresponding liability deconstruction element value (e.g., level ofpremium payments of the life insurance policy as the original asset), acredit rating associated with a custodial entity (e.g., an entityassociated with a transactional server) responsible for making theseries of payments of the liability deconstruction element, a creditrating of an entity issuing the original asset (e.g., the life insurancecompany responsible for the life insurance policy), and timingassociated with future cash flow of the asset deconstruction element(e.g., timing of a death benefit payment from the life insurance policyupon death of an insured person).

The value of the title 2 grouping is a function of the expectedliability payments associated with the liability deconstruction elements(e.g., life insurance policy premiums based on those insured andmortality table information), one or more asset deconstruction elements(e.g., death benefits), and a cash level or similar (e.g., any otherfinancial instrument to add value such that a net value of the title 2grouping is positive with respect to the life of the title 2 grouping).As an example, the cash asset may be produced by selling at least someof the asset deconstruction elements to produce cash to bundle into thetitle 2 grouping.

FIG. 7C is a logic diagram of an example of a method utilizingaugmenting assets that includes step 270 where a deconstruction approachmodule identifies a transactional server associated with a custodialentity to facilitate ongoing transactions of the financial system whenaugmented by an acquired augmenting asset bundle. The identifyingincludes one or more of interpreting a request, interpreting a queryresponse, declaring a competition winner, analyzing historicaltransaction information, identifying a desired risk level for an entityassociated with a transactional server, and interpreting riskinformation associated with entities of a plurality of transactionalservers.

The method continues at step 272 where the deconstruction approachmodule selects a deconstruction approach for each asset of the acquiredaugmenting asset bundle to produce asset deconstruction approachinformation, where an estimated value of deconstructed asset elementscompares favorably to one or more of a desired cash flow and a desiredvaluation lift and other funding requirements of a financial system foraugmentation. The selecting includes one or more of utilizing apredetermination, interpreting a request, interpreting historicalresults for various deconstruction approaches, analyzing data messagesfrom a data source where the data messages include current marketconditions, optimizing a level of fit for cash flow and for value for atleast a portion of the assets for two or more of the deconstructionapproaches to identify a presently superior deconstruction approach,where asset element valuation depends on risks associated with entitiesassociated with one or more of a plurality of servers of a communicationsystem, and outputting the asset deconstruction approach information toinclude one or more of an approach for each asset, a number of assets,identifiers of assets, and preliminary asset title transfer information.

The method continues at step 274 where a deconstruction modulefacilitates deconstruction of substantially each element of the acquiredaugmenting asset bundle utilizing the selected deconstruction approachto produce asset augmentation information. The facilitating includesperforming the deconstruction or requesting that a remote serverperforms the deconstruction utilizing the asset deconstruction approachinformation.

FIG. 8A is a schematic block diagram of another embodiment of acommunication system that includes the legacy server 22 of FIG. 1 , thetransactional server 18 of FIG. 1 , the augmentation server 24 of FIG. 1, and the control server 20 of FIG. 1 . The legacy server 22 includesthe diagnostic module 120 of FIG. 4A. The control server 20 includes theprocessing module 44 of FIG. 1 and the database 30 of FIG. 1 . Theprocessing module 44 includes the acquisition module 122 of FIG. 4A andthe augmentation module 124 of FIG. 4A. The communication systemfunctions to facilitate asset reconfiguration and reassignment.

In an example of operation of the facilitating asset reconfiguration andreassignment, the diagnostic module 120 determines to evaluate afinancial system associated with the legacy server 22. When evaluatingthe financial system, the diagnostic module 120 characterizes thefinancial system based on financial system information 130 to producedesired financial attributes 132 that includes a desired cash flow and adesired valuation lift.

The acquisition module 122 identifies augmenting asset preferences,accesses augmenting asset information 134 to extract candidate assetcharacteristics, down selects candidate assets that have characteristicsthat compare favorably to the augmenting asset preferences and to thedesired financial attributes 132, determines financial contributions ofeach of the down selected candidate assets, and selects an assetselection approach. The acquisition module 122 further completesselection of assets from the down selected candidate assets to producean augmenting asset bundle utilizing the selected asset selectionapproach, where an estimated financial contribution of the augmentingasset bundle compares favorably to the desired cash flow and valuationlift, and summarizes the augmenting asset bundle to reveal selectedasset characteristics to produce acquired augmenting asset bundleinformation 136.

The augmentation module 124 facilitates identification of a custodialentity and an associated transactional server 18, selects adeconstruction approach for the acquired augmenting asset bundle wherean estimated value of deconstructed asset elements compares favorably toone or more of the desired cash flow, the desired valuation lift, andother funding requirements (e.g., the transactional server 18 generatesan estimated value, the augmentation module 124 generates the estimatedvalue), generates title transfer information for the deconstructed assetelements, facilitates producing of the acquired augmenting asset bundleutilizing the deconstruction approach to produce the deconstructed assetelements (e.g., perform the deconstruction or request that anotherentity such as the legacy server 22 perform the deconstruction byissuing a request that includes selected asset titling information andthe selected asset deconstruction approach. For instance, theaugmentation module 124 issues asset augmentation information 138 to thelegacy server 22, where the asset augmentation information 138 includesthe selected asset titling information and the selected assetdeconstruction approach along with a request that the legacy server 22perform the deconstruction.

Having received the asset augmentation information 138, the legacyserver 22 performs the deconstruction of the augmenting asset bundle toproduce the deconstructed asset elements in accordance with the selectedasset deconstruction approach, re-bundles deconstructed asset elementsto produce two or more groupings, assigns title to each of the two ormore groupings in accordance with the received titling information, andissues asset and liability partitioning information 140 to thetransactional server 18, where the asset and liability partitioninginformation 140 includes asset deconstruction results and deconstructedasset element title information. For instance, a first title group ofdeconstructed elements is titled to the financial system of the legacyserver 22 (e.g., a pension system) and a second title group ofdeconstructed elements is titled to the entity associated with thecustodial entity transactional server 18.

Having received the asset and liability protection information 140 thetransactional server 18 issues liability settlement information 142 tothe augmentation server 24 in accordance with timing associated with aparticular group of deconstructed elements titled to either thetransactional server 18 or the legacy server 22 (e.g., life insurancepolicy premium payments, life insurance death benefit claims) andreceives corresponding asset settlement information 144 (e.g., lifeinsurance death benefit payments). The transactional server 18 issuessub-asset settlement information 146 to the legacy server 22 whenreceiving asset settlement information 144 to satisfy compensation forasset maturation in accordance with the titling information (e.g., aportion of the life insurance death benefit payments are forwarded tothe legacy server 22 for utilization in the financial system). Havingreceived a plurality of asset maturation payments (e.g., numeroussub-asset settlement information 146), the legacy server 22 facilitatesissuing of financial system output information 148 (e.g., financialtransactions to satisfy pension payments in accordance with a pensionschedule for each pension participant).

FIG. 8B is a logic diagram of another example of a method of enhancing alegacy asset base that includes step 280 where a legacy serverdetermines desired financial attributes of the financial systemsupported by a legacy asset base. For example, the legacy serverdetermines to evaluate the financial system and characterizes thefinancial system to estimate a desired cash flow and a desired valuationlift when the financial system is underperforming.

The method continues at step 282 where a control server facilitatesacquisition of an augmenting asset bundle to enhance the legacy assetbase. For example, the control server identifies augmenting assetpreferences, accesses augmenting asset information to extract candidateasset characteristics, down selects candidate assets that havecharacteristics that compare favorably to the augmenting assetpreferences, determines financial contributions of each of the downselected candidate assets, selects an asset selection approach,completes the selection from the down selected candidate assets toproduce the augmenting asset bundle utilizing the selected assetselection approach where an estimated financial contribution of theaugmenting asset bundle compares favorably to the desired cash flow anddesired valuation lift, and summarizes the augmenting asset bundle toreveal selected asset characteristics.

The method continues at step 284 where the control server facilitatesenhancement of the legacy asset base with the augmenting asset bundle toenable the financial system in accordance with the desired financialattributes. For example, the control server facilitates identificationof a custodial entity associated with a transactional server, selects adeconstruction approach for the acquired augmenting asset bundle wherean estimated value of two or more groupings of deconstructed assetelements compares favorably to one or more of the desired cash flow, thedesired valuation lift, and other funding requirements, generatestitling information for the two or more groupings of the deconstructedasset elements, and facilitates producing of the two or more groupingsof deconstructed asset elements utilizing the deconstruction approach.

FIG. 9A is a schematic block diagram of another embodiment of acommunication system that includes the legacy server 22 of FIG. 1 , thetransactional server 18 of FIG. 1 , the augmentation server 24 of FIG. 1, and the control server 20 of FIG. 1 . The legacy server 22 includesthe diagnostic module 120 of FIG. 4A. The control server 20 includes theprocessing module 44 of FIG. 1 and the database 30 of FIG. 1 . Theprocessing module 44 includes the acquisition module 122 of FIG. 4A andthe augmentation module 124 of FIG. 4A. The communication systemfunctions to facilitate asset reconfiguration and reassignment.

In an example of operation of the facilitating asset reconfiguration andreassignment, the diagnostic module 120 determines to evaluate return oninvestment (ROI) information associated with the legacy server 22. SuchROI information to be associated with one or more present or futureasset bases, where an investment is expected to produce a return withvarious minimums for financial metrics such as a minimum ROI level, atime frame to achieve various absolute returns, minimum level ofmagnitudes of returns, etc. The legacy asset base will eventuallyproduce returns that are summarized by the legacy server 22 as financialreturn information 292 (e.g., cash flow information, balance sheetinformation. When evaluating the ROI, the diagnostic module 120characterizes the one or more asset bases from ROI information 290 toproduce desired financial attributes 132 that includes a desired cashflow and a desired valuation lift.

The acquisition module 122 identifies augmenting asset preferences,accesses augmenting asset information 134 to extract candidate assetcharacteristics, down selects candidate assets that have characteristicsthat compare favorably to the augmenting asset preferences and to thedesired financial attributes 132, determines financial contributions ofeach of the down selected candidate assets, and selects an assetselection approach. The acquisition module 122 further completesselection of assets from the down selected candidate assets to producean augmenting asset bundle utilizing the selected asset selectionapproach, where an estimated financial contribution of the augmentingasset bundle compares favorably to the desired cash flow and valuationlift, and summarizes the augmenting asset bundle to reveal selectedasset characteristics to produce acquired augmenting asset bundleinformation 136.

The augmentation module 124 facilitates identification of a custodialentity and an associated transactional server 18, selects adeconstruction approach for the acquired augmenting asset bundle wherean estimated value of deconstructed asset elements compares favorably toone or more of the desired cash flow, the desired valuation lift, andother funding requirements (e.g., the transactional server 18 generatesan estimated value, the augmentation module 124 generates the estimatedvalue), generates title transfer information for the deconstructed assetelements, facilitates producing of the acquired augmenting asset bundleutilizing the deconstruction approach to produce the deconstructed assetelements (e.g., perform the deconstruction or request that anotherentity such as the legacy server 22 perform the deconstruction byissuing a request that includes selected asset titling information andthe selected asset deconstruction approach. For instance, theaugmentation module 124 issues asset augmentation information 138 to thelegacy server 22, where the asset augmentation information 138 includesthe selected asset titling information and the selected assetdeconstruction approach along with a request that the legacy server 22perform the deconstruction.

Having received the asset augmentation information 138, the legacyserver 22 performs the deconstruction of the augmenting asset bundle toproduce the deconstructed asset elements in accordance with the selectedasset deconstruction approach, re-bundles deconstructed asset elementsto produce two or more groupings, assigns title to each of the two ormore groupings in accordance with the received titling information, andissues asset and liability partitioning information 140 to thetransactional server 18, where the asset and liability partitioninginformation 140 includes asset deconstruction results and deconstructedasset element title information. For instance, a first title group ofdeconstructed elements is titled to the asset base of the legacy server22 (e.g., a general investment fund) and a second title group ofdeconstructed elements is titled to the entity associated with thecustodial entity transactional server 18.

Having received the asset and liability protection information 140 thetransactional server 18 issues liability settlement information 142 tothe augmentation server 24 in accordance with timing associated with aparticular group of deconstructed elements titled to either thetransactional server 18 or the legacy server 22 (e.g., life insurancepolicy premium payments, life insurance death benefit claims) andreceives corresponding asset settlement information 144 (e.g., lifeinsurance death benefit payments). The transactional server 18 issuessub-asset settlement information 146 to the legacy server 22 whenreceiving asset settlement information 144 to satisfy dividend paymentsor similar for asset maturation in accordance with the titlinginformation (e.g., a portion of the life insurance death benefitpayments are forwarded to the legacy server 22 for utilization in theasset base). Having received a plurality of asset maturation payments(e.g., numerous sub-asset settlement information 146), the legacy server22 facilitates issuing of the financial return information 292 (e.g.,financial transactions to satisfy general investment fund payments inaccordance with a dividend payment schedule for each investment fundparticipant).

FIG. 9B is a logic diagram of another example of a method of enhancing alegacy asset base that includes step 300 where a legacy serverdetermines desired financial attributes of an ROI (e.g., of a generalinvestment fund or similar). For example, the legacy server determinesto evaluate the ROI of the legacy asset base and characterizes theacid-base to estimate a desired cash flow and a desired valuation lift.

The method continues at step 302 where a control server facilitatesacquisition of an augmenting asset bundle to enhance the legacy assetbase. For example, the control server identifies augmenting assetpreferences, accesses augmenting asset information to extract candidateasset characteristics, down selects candidate assets that havecharacteristics that compare favorably to the augmenting assetpreferences, determines financial contributions of each of the downselected candidate assets, selects an asset selection approach,completes the selection from the down selected candidate assets toproduce the augmenting asset bundle utilizing the selected assetselection approach where an estimated financial contribution of theaugmenting asset bundle compares favorably to the desired cash flow anddesired valuation lift, and summarizes the augmenting asset bundle toreveal selected asset characteristics.

The method continues at step 304 where the control server facilitatesenhancement of the legacy asset base with the augmenting asset bundle toenable the legacy asset in accordance with the desired financialattributes. For example, the control server facilitates identificationof a custodial entity associated with a transactional server, selects adeconstruction approach for the acquired augmenting asset bundle wherean estimated value of two or more groupings of deconstructed assetelements compares favorably to one or more of the desired cash flow, thedesired valuation lift, and other funding requirements, generatestitling information for the two or more groupings of the deconstructedasset elements, and facilitates producing of the two or more groupingsof deconstructed asset elements utilizing the deconstruction approach toenable future results of the legacy asset base to compare favorably tothe desired financial attributes.

FIG. 10A is a schematic block diagram of another embodiment of acommunication system that includes the plurality of N augmentationsystems 14 of FIG. 1 , the conversion server 16 of FIG. 1 , thetransactional server 18 of FIG. 1 , and the control server 20 of FIG. 1. Each augmentation system 14 includes a portion of the network 28 ofFIG. 1 , the plurality of user devices 32 of FIG. 1 , the plurality ofsubscriber devices 34 of FIG. 1 , and the augmentation server 24 of FIG.1 . The control server 20 includes the processing module 44 FIG. 1 andthe database 30 of FIG. 1 . The processing module 44 includes thediagnostic module 120 of FIG. 4A, the acquisition module 122 of FIG. 4A,and the augmentation module 124 of FIG. 4 . The communication systemfunctions to facilitate asset reconfiguration and reassignment.

In an example of operation of the facilitating of the assetreconfiguration and reassignment, the acquisition module 122 determineswhether to update an acquired augmenting asset bundle. As a particularexample, the acquisition module 122 receives updated desired financialattributes 314 from the diagnostic module 120 based on updated financialsystem information 312 from the conversion server 16 and detects that achange has occurred that will drive updated desired financial attributes314 (e.g., a new desired cash flow is detected, a new desired valuationlift is detected).

As another particular example, the acquisition module 122 receivesupdated augmenting asset information 310 from one or more of a userdevice 32, a subscriber device 34, and the augmentation server 24, anddetects that an attribute of an augmenting asset of the acquiredaugmented asset bundle compares favorably to an attribute thresholdlevel (e.g., interpret updated augmenting asset information 310 from auser device 32 to extract the attribute, compare the attribute to acorresponding attribute threshold level, and indicate the favorablecomparison when the attribute compares favorably to the attributethreshold level). Examples of attributes include user demographics, userlifestyle, user location user interests, user illness, user domicilelocation, user work location user career field, user family connections,user social connections user leisure time activities, user nutritioninformation, user DNA information, weather conditions associated with aproximal location to a user, and/or any other attribute associated withone or more users that may impact valuation of associated assets of anaugmentation system. For instance, the acquisition module 122 detects alifestyle change of a person associated with the user device 32, wherethe person is associated with a life insurance policy asset of theaugmenting assets.

When updating the acquired augmenting asset bundle, the acquisitionmodule 122 facilitates further augmenting asset acquisition to produceupdated acquired augmenting asset bundle information 316. For example,the acquisition module 122 identifies augmenting asset preferences,accesses the updated augmenting asset information 310 to extractcandidate asset characteristics, down selects candidate assets that haveattributes that compare favorably to the augmenting asset preferences,determines financial contributions of each of the down selectedcandidate assets, and selects an asset selection approach (e.g., keepsome prior assets, swaps and prior assets, add more assets, remove someassets). The selecting may be based on one or more of apredetermination, a request, a query response, and a previously utilizedasset selection approach that is associated with favorable financialresults.

When acquiring more assets, the acquisition module 122 completes theselection from the down selected candidate assets to produce the updatedaugmenting asset bundle utilizing the selected asset selection approachwhere an estimated financial contribution of the augmenting asset bundlecompares favorably to a desired cash flow and a desired valuation lift.The acquisition module 122 summarizes the updated acquired asset bundleto reveal further selected asset characteristics included in updatedacquired augmenting asset bundle information 316.

The augmentation module 124 facilitates updating of the acquiredaugmenting asset bundle to produce updated asset augmentationinformation 318. For example, the augmentation module 124 identifies acustodial entity associated with the transactional server 18, selects adeconstruction approach for the updated acquired augmenting assetbundle, where an estimated value of remaining deconstructed assetelements combined with further acquired deconstructed asset elements,when re-bundled in two or more groups, compares favorably to one or moreof the desired cash flow, the desired valuation lift, and other fundingrequirements.

The augmentation module 124 generates updated titling information forthe totality of deconstructed asset elements as a result of a newre-bundling plan and facilitates the construction of an updated acquiredaugmenting asset bundle utilizing the deconstruction approach to producethe further deconstructed asset elements (e.g., perform thedeconstruction or request that another entity such as the conversionserver 16 perform the deconstruction by issuing the updated assetaugmentation information 318 to the conversion server 16). The updatedasset augmentation information 318 includes one or more of the assettitling information, the selected asset deconstruction approach, and arequest to perform the deconstruction.

The conversion server 16 issues updated asset and liability partitioninginformation 320 to the transactional server 18 based on the updatedasset augmentation information 318. The transactional server 18 issuesliability settlement information 142 to the augmentation server 24 fromtime to time and receives asset settlement information 144 from theaugmentation server 24.

FIG. 10B is a logic diagram of an example of a method of updating anacquired augmenting asset bundle that includes step 330 where anacquisition module determines whether to update an acquired augmentedasset bundle. The determining may be based on one or more ofinterpreting updated desired financial attributes based on updatedfinancial system information and detecting that an attribute of anaugmenting asset of the acquired augmenting asset bundle comparesfavorably to an attribute threshold level (e.g., interpret updatedaugmenting asset information to extract the attribute, compare theattribute to a corresponding attribute threshold level, and indicate afavorable comparison when the attribute compares favorably to theattribute threshold level).

When updating, the method continues at step 332 where the acquisitionmodule facilitates further augmenting asset acquisition to produceupdated acquired augmented asset bundle information. For example, theacquisition module identifies augmenting asset preferences, accessesupdated augmenting asset information to extract candidate assetcharacteristics, down selects candidate assets that have attributes thatcompare favorably to the augmenting asset preferences, determinesfinancial contributions of each of the down selected candidate assets,selects an asset selection approach, completes the selection from thedown selected candidate assets to produce the updated augmenting assetbundle utilizing the selected asset selection approach where anestimated financial contribution of the augmenting asset bundle comparesfavorably to a desired cash flow and a desired valuation lift, andsummarize the updated augmenting asset bundle to reveal further selectedasset characteristics.

The method continues at step 334 where an augmentation modulefacilitates updating of an acquired augmenting asset bundle to produceupdated asset augmentation information. For example, the augmentationmodule identifies a custodial entity of an associated transactionalserver, selects a deconstruction approach for the updated acquiredaugmented asset bundle where an estimated value of remainingdeconstructed asset elements combined with further acquireddeconstructed asset elements compares favorably to one or more of thedesired cash flow, the desired valuation lift, and other fundingrequirements, generates updated titling information for the totality ofdeconstructed asset elements, facilitates the construction of an updatedacquired augmenting asset bundle utilizing the deconstruction approachto produce further deconstructed asset elements, where the transactionalserver utilizes the further elements.

FIG. 11A is a schematic block diagram of another embodiment of acommunication system that includes the plurality of N augmentationsystems 14 of FIG. 1 , the conversion server 16 of FIG. 1 , thetransactional server 18 of FIG. 1 , and the control server 20 of FIG. 1. Each augmentation system 14 includes a portion of the network 28 ofFIG. 1 , the plurality of user devices 32 of FIG. 1 , the plurality ofsubscriber devices 34 of FIG. 1 , and the augmentation server 24 of FIG.1 . The control server 20 includes the processing module 44 FIG. 1 andthe database 30 of FIG. 1 . The processing module 44 includes thediagnostic module 120 of FIG. 4A, the acquisition module 122 of FIG. 4A,and the augmentation module 124 of FIG. 4 . The communication systemfunctions to facilitate asset reconfiguration and reassignment.

In an example of operation of the facilitating of the assetreconfiguration and reassignment, the acquisition module 122 determineswhether to update an asset base associated with the conversion server 16(e.g., where a pension system sponsor is associated with the conversionserver 16). As a particular example, the acquisition module 122 receivesongoing desired financial attributes 344 from the diagnostic module 120based on ongoing financial system information 342 from the conversionserver 16 and detects that a change has occurred that will drive ongoingdesired financial attributes 344 (e.g., a new desired cash flow isdetected, a new desired valuation lift is detected).

As another particular example, the acquisition module 122 receives anindication from one or more of the transactional server 18, theconversion server 16, the augmentation server 24, one or more userdevices 32, and one or more subscriber devices 34, that a triggercondition has occurred associated with one or more of the asset base andor with one or more available assets associated with one or more of theaugmentation systems 14. For example, the acquisition module 122interprets ongoing augmenting asset information 340 from a first userdevice 32, where the interpretation indicates that an asset associatedwith the user of the first user device 32 has favorable attributes ascompared to augmenting asset preferences and may be available forpurchase.

When augmenting the asset base, the acquisition module 122 facilitatesaugmenting asset acquisition utilizing solicitation of a plurality ofassets associated with one or more augmentation systems 14 to produceongoing acquired augmenting asset bundle information 348. For example,the acquisition module 122 identifies the augmenting asset preferences,accesses the ongoing augmenting asset information 342 extract candidateasset characteristics, down selects candidate assets that comparefavorably to the augmenting asset preferences, determines financialcontributions of each of the down selected candidate assets, selects anasset selection approach, complete selection from the down selectedcandidate assets to produce an updated augmenting asset bundle utilizingthe selected asset selection approach where an estimated financialcontribution of the augmenting asset bundle compares favorably todesired cash flow and desired valuation lift, and summarizes the updatedaugmenting asset bundle to reveal further selected asset characteristicsin ongoing acquired augmenting asset bundle information 348, where theacquisition module 122 issues solicitation information 346 to thecorresponding one or more augmentation systems 14 to invoke a newagreement to sell an asset (e.g., sends a solicitation message to thefirst user device 32), and completes the acquiring of the selectedassets.

The augmentation module 124 facilitates updating of the acquiredaugmenting asset bundle to produce optimized asset augmentationinformation 350. For example, the augmentation module 124 identifies acustodial entity associated with the transactional server 18, selects adeconstruction approach for the updated acquired augmenting assetbundle, where an estimated value of remaining deconstructed assetelements combined with further acquired deconstructed asset elements,when re-bundled in two or more groups, compares favorably to one or moreof the desired cash flow, the desired valuation lift, and other fundingrequirements.

The augmentation module 124 generates updated titling information forthe totality of deconstructed asset elements as a result of a newre-bundling plan and facilitates the construction of an updated acquiredaugmenting asset bundle utilizing the deconstruction approach to producethe further deconstructed asset elements (e.g., perform thedeconstruction or request that another entity such as the conversionserver 16 perform the deconstruction by issuing the updated assetaugmentation information 318 to the conversion server 16). The optimizedasset augmentation information 350 includes one or more of the assettitling information, the selected asset deconstruction approach, and arequest to perform the deconstruction.

The conversion server 16 issues optimized asset and liabilitypartitioning information 352 to the transactional server 18 based on theoptimized asset augmentation information 350. The transactional server18 issues liability settlement information 142 to the augmentationserver 24 from time to time and receives asset settlement information144 from the augmentation server 24.

FIG. 11B is a logic diagram of another example of a method of updatingan acquired augmenting asset bundle that includes step 360 where anacquisition module determines whether to augment an asset base. Whenupdating the asset base, the method continues at step 362 where theacquisition module facilitates further augmenting asset acquisitionutilizing solicitation of a plurality of assets associated with one ormore augmentation systems to produce on-going acquired augmented assetbundle information. The method continues at step 364 where anaugmentation module facilitates updating of an acquired augmenting assetbundle to produce optimized asset augmentation information.

FIGS. 12A-12E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forservicing a plurality of rived longevity-contingent instruments within acomputing system. The computing system includes data sources 26-1through 26-N, the augmentation server 24 of FIG. 1 , the transactionalserver 18 of FIG. 1 , and legacy servers 22-1 through 22-2. In anembodiment, the data sources 26-1 through 26-N are implemented utilizingthe data source 26 of FIG. 1 . In an embodiment, the legacy servers 22-1through 22-2 are implemented utilizing the legacy server 22 of FIG. 1 ,where legacy server 22-1 is associated with a pension system and legacyserver 22-2 is associated with one or more sponsors associated with thepension system. The transactional server 18 includes the processingmodule 44 of FIG. 1 and the database 30 of FIG. 1 .

The plurality of rived longevity-contingent instruments includes a poolof life insurance policies (e.g., the instruments), where the policieshave been rived (e.g., split of benefit ownership from premium liabilityresponsibility). Each longevity-contingent instrument is associated witha premium payment stream (e.g., series of premium payments). Forexample, an insurance company of a first life insurance policy requiresa monthly premium payment to maintain the first life insurance policy inforce. Together, the pool of life insurance policies is associated witha plurality of premium payment streams.

A financial offering that includes the pool of life insurance policiesrequires an aggregated payment of the plurality of premium paymentstreams associated with the pool of life insurance policies. In anembodiment, the one or more sponsors associated with the legacy servers22-1 through 22-2 are liable for the aggregated payment of the pluralityof periodic premium payments in accordance with a rive approach 682. Therive approach 682 is discussed in greater detail with regards to FIG.12C.

Each longevity-contingent instrument is further associated with a payout(e.g., death benefit) when a longevity status changes, e.g., a death ofan insured person associated with the life insurance policy of thelongevity-contingent instrument. For example, when the insured personpasses, the life insurance company of the first life insurance policyprovides payment of the payout to an entity associated with ownership ofthe first life insurance policy.

Riving of the policies splits the policy to associate liability ofperiodic premium payments with one or more debtors (e.g., sponsors) andto associate the policy payout with one or more benefactors (e.g., apension and a sponsor). For example, the riving results in associatingmultiple sponsors of a common union pension with the liability ofperiodic premium payments. As another example, the riving results inassociating the multiple sponsors of the common union pension and thecommon union pension with the policy payout.

The servicing of the plurality of longevity-contingent instrumentincludes steps associated with both the payouts upon longevity statuschange and the payment of the premium payment streams. The method of theservicing is discussed in greater detail with reference to FIGS.15A-15E.

FIG. 12A illustrates an example of operation of steps of a method forthe servicing of the plurality of longevity-contingent instrumentswhere, in a first step, the processing module 44 interprets a digitallyencoded data packet from another computing device to produce a firstlongevity indicator of a first longevity-contingent instrument of aplurality of longevity-contingent instruments. The firstlongevity-contingent instrument is rived in accordance with the riveapproach 682 to produce a first sub-asset of a plurality of sub-assetsand a first sub-liability of a plurality of sub-liabilities. The firstsub-liability is associated with a first premium payment stream of aplurality of premium payment streams of the plurality ofsub-liabilities.

A first death-notification of a multitude of death-notifications isencoded to produce the digitally encoded data packet. For example, theprocessing module 44 receives a multitude of death-notifications 662-1through 662-N from data sources 26-1 through 26-N. The processing module44 decodes the multitude of death-notifications to producedeath-notification information. The processing module 44 accesses thedatabase 30 to extract a plurality of insured person identifiers of theplurality of longevity-contingent instruments from longevity-contingentinstrument information 660. A first insured person identifier of theplurality of insured person identifiers is associated with the firstlongevity-contingent instrument. The processing module 44 generates thefirst longevity indicator 664 to indicate a deceased status when thedeath-notification information includes a deceased person identifierthat substantially matches the first insured person identifier of thefirst longevity-contingent instrument.

In another example, the processing module 44 interprets asset settlementinformation 144 to produce an indication of payment of the payout 674.The processing module 44 generates the first longevity indicator 664when the payment of the payout 674 includes the deceased personidentifier that substantially matches the first insured personidentifier of the first longevity-contingent instrument.

In yet another example, the processing module 44 interprets either ofthe asset settlement information 144 and a correspondingdeath-notification 662-1 to produce a longevity status change 676. Theprocessing module 44 generates the first longevity indicator 664 whenthe longevity status change 676 includes the deceased person identifierthat substantially matches the first insured person identifier of thefirst longevity-contingent instrument.

FIG. 12B further illustrates the example of the servicing of theplurality of longevity-contingent instruments where, having produced thefirst longevity indicator 664, in a second step, the processing module44 updates a first longevity status indicator 666 for the firstlongevity-contingent instrument within the database 30 utilizing thefirst longevity indicator to produce an updated first longevity statusindicator. For example, the processing module 44 produces the updatedfirst longevity status indicator to indicate a benefit status when thefirst longevity indicator 664 indicates that the insured person hasdeceased.

Having updated the first longevity status indicator 666, when theupdated first longevity status indicator is associated with the benefitstatus, in a third step, the processing module 44 determines a payout678 associated with the first sub-asset. The determining the payout 678includes a variety of approaches. A first approach includes interpretinga payment notification message 672. For example, the processing module44 interprets the asset settlement information 144 to produce thepayment notification message 672, where the payment notification message672 includes the payout 678. In another example, the processing module44 interprets the asset settlement information 144 to produce theindication of payment of the payout 674, where the indication of paymentof the payout 674 includes the payout 678.

A second approach to determine the payout 678 includes accessing thedatabase 30 to extract a face value of the first longevity-contingentinstrument. For example, the processing module 44 accesses thelongevity-contingent instrument information 660 to extract the facevalue (e.g., a stated value of an associated life insurance policy).

A third approach to determine the payout 678 includes accessing thedatabase 30 to extract a benefit value (e.g., an agreed to value) of thefirst sub-asset. For example, the processing module 44 accessessub-asset information 690 to extract the benefit value.

Alternatively, or in addition to, the processing module 44 indicatesthat the first sub-asset has matured. For example, the processing moduleupdates the sub-asset information 690 to indicate that the sub-asset hasmatured (e.g., to benefit payout).

FIG. 12C further illustrates the example of the servicing of theplurality of longevity-contingent instruments where the processingmodule 44, having identified the payout 678, in a fourth step determinesa first portion of the payout 680 to associate with a premium cashescrow 668 in accordance with the rive approach 682. The associationenables subsequent utilization of the premium cash escrow 668 to fundthe aggregated payment of the plurality of premium payment streams onbehalf of the one or more debtors.

The rive approach includes a variety of approaches. The approachesinclude a surplus approach where a balance associated with the premiumcash escrow 668 is maintained at a level that is more than enough tomake the aggregated premium payment streams. The approaches furtherinclude a deficit approach where the balance associated with the premiumcash escrow 668 is maintained at a level that is less than enough tomake the aggregated premium payment streams (e.g., another party such asa pension sponsor is liable to make up differences).

The approaches further include a breakeven approach where the balanceassociated with the premium cash escrow 668 is maintained at a levelthat is just enough to make the aggregated premium payment streams. Theapproaches further include a pro rata approach where the first portionis in accordance with a negotiated percentage of the payout (e.g.,always 50% or even 40%). The approaches further include a consistencyapproach where the balance associated with the premium cash escrow 668receives a stream of constant inflows to support the aggregated premiumpayment streams.

When the rive approach 682 includes the surplus approach, thedetermining of the first portion of the payout 680 includes calculatingthe first portion of the payout such that a sum of a plurality of firstportion payouts within a first time frame is greater than a sum of asubset of the plurality of premium payment streams for the first timeframe. When the rive approach 682 includes the deficit approach, thedetermining of the first portion of the payout 680 includes calculatingthe first portion of the payout such that the sum of the plurality offirst portion payouts within the first time frame is less than the sumof the subset of the plurality of premium payment streams for the firsttime frame.

When the rive approach 682 includes the break-even approach, thedetermining of the first portion of the payout 680 includes calculatingthe first portion of the payout such that the sum of the plurality offirst portion payouts within the first time frame is substantially thesame as the sum of the subset of the plurality of premium paymentstreams for the first time frame. When the rive approach 682 includesthe pro rata approach, the determining of the first portion of thepayout 680 includes establishing the first portion of the payout inaccordance with a pre-determined percentage of the payout. When the riveapproach 682 includes the consistency approach, the determining of thefirst portion of the payout 680 includes establishing the first portionof the payout in accordance with a pre-determined first portion level(e.g., a default constant amount).

Having determined the first portion of the payout 680, the processingmodule 44, in a fifth step determines a second portion of the payout 686to associate with a benefit cash account 670 based on the first portionof the payout 680 and in accordance with the rive approach 682. Thebenefit cash account 670 is associated with the one or more benefactors.The determining of the second portion of the payout 686 includes avariety of approaches. The approaches include the pro rata approach, theconsistency approach, and a difference approach.

When the rive approach includes the pro rata approach, the determiningof the second portion of the payout 686 includes establishing the secondportion of the payout 686 in accordance with a pre-determined percentageof the payout. For example, the processing module 44 multiplies thepredetermined percentage by the payout 678 to produce the second portionof the payout 686 (e.g., 60% of the payout).

When the rive approach includes the consistency approach, thedetermining of the second portion of the payout 686 includesestablishing the second portion of the payout 686 in accordance with apre-determined second portion level (e.g., a constant amount). Forexample, the processing module 44 sets the second portion of the payout686 to be a fixed number based on the predetermined second portion level(e.g., a flat $100,000).

When the rive approach includes the difference approach, the determiningof the second portion of the payout 686 includes establishing the secondportion of the payout in accordance with a difference between the payoutand the first portion of the payout (e.g., what's leftover). Forexample, the processing module 44 subtracts the first portion of thepayout 680 from the payout 678 to produce the second portion of thepayout 686 (e.g., $1 million payout minus $480,000 first portion equals$520,000).

Alternatively, or in addition to, the processing module 44 determines athird portion of the payout. For instance, the payout 678 equals the sumof the first through third portions, where the third portion is aservice fee. In yet another alternative, the processing moduledetermines further portions of the payout when more than one benefactordirectly receives a portion of the payout 678 (e.g., multiple pensionsassociated with the plurality of longevity-contingent assets).

FIG. 12D further illustrates the example of the servicing of theplurality of longevity-contingent instruments where the processingmodule 44, in sixth step, facilitates reconciling of the first portionof the payout 680 to the premium cash escrow 668 and the second portionof the payout 686 to the benefit cash account 670. For example, theprocessing module 44 increments the premium cash escrow 668 of thedatabase 30 by an amount of the first portion of the payout 680.Alternatively, or in addition to, the processing module 44 issues apayment message to another server associated with the premium cashescrow 668 (e.g., a debtor). As another example, the processing module44 increments the benefit cash account 670 of the database 30 by anamount of the second portion of the payout 686. Alternatively, or inaddition to, the processing module 44 issues a payment message toanother server associated with the benefit cash account 670 (e.g., abenefactor).

Having facilitated the reconciling of the first portion of the payout680 and the second portion of the payout 686, in a seventh step theprocessing module 44 facilitates the aggregated payment of the pluralityof premium payment streams utilizing the premium cash escrow 668 and oneor more premium offsets 688-1 and 688-2 from the one or more debtors(e.g., via their legacy servers 22-1 and 22-2). For example, theprocessing module 44 accrues premium payments 684 utilizing a portion ofthe premium cash escrow 668, determines a level of a required payment ofthe premium payment streams, calculates a difference between the accruedpremium payment 684 and the level of required payment to produce asupplementing level, and obtains the supplementing level of funds fromthe legacy servers 22-1 and 22-2 via premium offsets 688-1 and 688-2.

Having obtained the portion of the premium cash escrow 668, the premiumoffsets 688-1, and the premium offsets 688-2, the processing module 44sums the portion of the premium cash escrow 668, the premium offset688-1, and the premium offset 688-2 to produce the premium payments 684.Having produced the premium payments 684, the processing module 44issues liability settlement information 142 to the augmentation server24, where the liability settlement information 142 pertains to thepremium payments 684.

FIG. 12E further illustrates the example of the servicing of theplurality of longevity-contingent instruments where, in an eight stepthe processing module 44 facilitates payment from the benefit cashaccount 670 to the one or more benefactors. For example, the processingmodule 44 issues sub-asset settlement information 146 to the legacyserver 22-1 that is associated with the pension system, where thesub-asset settlement information 146 includes a portion of the benefitcash account 670 (e.g., the second portion of the payout 686).Alternatively, or in addition to, the processing module 44 issues thesecond portion of the payout 686 to another server associated with oneor more other benefactors.

Having facilitated the payment of the benefit cash account 670, theprocessing module 44, from time to time in a nineth step, adjusts therive approach 682 to favor increasing the second portion of the payoutwhen a first sum of a first plurality of second portion payouts within afirst time frame is less than a first sum of a first subset of theplurality of premium payment streams for the first time frame. Forexample, the processing module 44 increases the percentage of the secondportion of the payout to bolster the premium payments.

Alternatively, the processing module 44, from time to time in the ninethstep, adjusts the rive approach to favor decreasing the second portionof the payout when a second sum of a second plurality of second portionpayouts within a second time frame is greater than a second sum of asecond subset of the plurality of premium payment streams for the secondtime frame. For example, the processing module 44 decreases thepercentage of the payout 686 to not overfund the premium payments.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 13A-13E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method for rivinglongevity-contingent instruments within a computing system. Thecomputing system includes a benefactor server 700, a debtor server 702,user devices 32-1 through 32-N, longevity-contingent instrument providerservers 704-1 through 704-M, and the control server 20 of FIG. 1 . In anembodiment, the benefactor server 700 and the debtor server 702 areimplemented utilizing the legacy server 22 of FIG. 1 , where thebenefactor server 700 is associated with at least one pension system andthe debtor server 702 is associated with at least one sponsor associatedwith the at least one pension system. In an embodiment, the user devices32-1 through 32-N are implemented utilizing the user devices 32 of FIG.1 . In an embodiment, the longevity-contingent instrument providerservers 704-1 through 704-M are implemented utilizing the augmentationserver 24 of FIG. 1 . The control server 20 includes the processingmodule 44 of FIG. 1 and the database 30 of FIG. 1 .

FIG. 13A illustrates an example of operation of steps of a method forthe riving of the longevity-contingent instruments where, in a firststep, the processing module 44 interprets digitally encoded riveparameters from one or more of a benefactor computing device (e.g., thebenefactor server 700) and a debtor computing device (e.g., the debtorserver 702) to produce rive approach requirements 714. The interpretingincludes a series of operations. A first operation includes decoding afirst subset of the digitally encoded rive parameters received from thebenefactor computing device to produce asset rive parameters. Forexample, the processing module 44 decodes digitally encoded riveparameters from the benefactor server 700 to produce asset riveparameters 710. The asset rive parameter 710 includes one or more of arequired net cash flow pattern, a target investment yield rate, and amaximum initial benefactor contribution level.

A second operation includes decoding a second subset of the digitallyencoded rive parameters received from the debtor computing device toproduce liability rive parameters. For example, the processing module 44decodes digitally encoded rive parameters from the debtor server 702 toproduce liability rive parameter 712. The liability rive parameters 712includes one or more of a maximum contribution cash flow pattern and amaximum initial debtor contribution level. A third operation includesaggregating the asset rive parameters 710 and the liability riveparameters 712 to produce the rive approach requirements 714.

Having produced the rive approach requirements 714, in a second step,the processing module 44 determines a rive approach 682 for riving a setof longevity-contingent instruments of a multitude of availablelongevity-contingent instruments based on the rive approach requirements714. A first longevity-contingent instrument of the set oflongevity-contingent instruments includes a first face value benefit(e.g., death benefit) and a first premium payment stream. A secondlongevity-contingent instrument of the set of longevity-contingentinstruments includes a second face value benefit and a second premiumpayment stream. When available (e.g., when an insured person passes andthe death benefit is provided), a first portion of the first face valuebenefit is utilized to fund at least some of the second premium paymentstream in accordance with the rive approach 682. The premium paymentstream includes series of time-certain obligated payments to maintainthe corresponding longevity-contingent instrument (e.g., with acorresponding provider, i.e. insurance company).

The determining of the rive approach 682 includes one of a variety ofways. A first way, when the rive approach requirements indicate that afirst allocated portion of the plurality of sub-assets is to be greaterthan the plurality of sub-liabilities, includes establishing the riveapproach as a surplus approach. A second way, when the rive approachrequirements indicate that the first allocated portion of the pluralityof sub-assets is to be less than the plurality of sub-liabilitiesincludes establishing the rive approach as a deficit approach. A thirdway, when the rive approach requirements indicate that the firstallocated portion of the plurality of sub-assets is to be substantiallythe same as the plurality of sub-liabilities includes establishing therive approach as a break-even approach.

A fourth way of determining the rive approach 682, when the riveapproach requirements indicate that the first allocated portion of theplurality of sub-assets is to be a pre-determined percentage of theplurality of sub-assets includes establishing the rive approach as a prorata approach. A fifth way, when the rive approach requirements indicatethat the first allocated portion of the plurality of sub-assets is to bea pre-determined first portion level includes establishing the riveapproach as a consistency approach.

FIG. 13B further illustrates the example of the riving of thelongevity-contingent instruments where, having determined the riveapproach 682, in a third step, the processing module 44 analyzes asubset of the multitude of available longevity-contingent instruments toproduce characterization information 720. The subset of the multitude ofavailable longevity-contingent instruments includes the firstlongevity-contingent instrument 722 and the second longevity-contingentinstrument 724. The characterization information 720 includes firstcharacterization information for the first longevity-contingentinstrument 722 and second characterization information for the secondlongevity-contingent instrument 724.

The multitude of available longevity-contingent instruments aregenerally available from one or both of a primary market and a secondarymarket. Accessing the primary market includes obtaining thelongevity-contingent instruments directly from initial policyholders(e.g., the originally insured). Accessing the secondary market includesobtaining the longevity-contingent instruments from brokers andproviders, where the longevity-contingent instruments have changed handsfrom the initial policyholders to one or more intermediaries (e.g., thebrokers, etc.).

The analyzing of the subset of the multitude of availablelongevity-contingent instruments to produce the characterizationinformation includes several sub-steps. A first sub-step includesaccessing the multitude of available longevity-contingent instruments.For example, the processing module 44 receives primary marketlongevity-contingent instrument information 716 from one or more of theuser devices 32-1 through 32-N. A first instance includes the userdevice 32-1 issuing the primary market longevity-contingent instrumentinformation 716 to the control server 20 in an unsolicited fashion whendesiring to offer a life insurance policy for sale. A second instanceincludes the control server 20 receiving the primary marketlongevity-contingent instrument information 716 from the user device32-2 in response to a solicitation message from the control server 20.

As another example of accessing a multitude of availablelongevity-contingent instruments, the processing module 44 receives oneor more of secondary market longevity-contingent instrument information718-1 through 718-M from one or more of the longevity-contingentinstrument provider servers 704-1 through 704-M. The receiving includesreceiving the information in an unsolicited fashion and receiving theinformation in response to the control server 20 issuing a solicitation.

Having accessed the multitude of available longevity-contingentinstruments, a second sub-step to analyze the subsets of the multitudeof available longevity-contingent instruments includes determining thefirst characterization information to include one or more elements. Afirst element includes a first estimated timeframe for payout of thefirst face value benefit (e.g., generate a life expectancy based on oneor more of insured age, gender, smoker, health impairments, historicallife expectancy data, etc.). A second element includes a present valueof the first face value benefit utilizing the first estimated timeframe(e.g., generate a present value range for a range of discounted cashflow analysis interest rates and for a range around the first estimatetimeframe, i.e., dither the life expectancy). A third element includes apresent value of the first premium payment stream.

A third sub-step to analyze the subsets of the multitude of availablelongevity-contingent instruments includes determining the secondcharacterization information to include one or more further elements. Afirst further element includes a second estimated timeframe for payoutof the second face value benefit. A second further element includes apresent value of the second face value benefit utilizing the secondestimated timeframe. A third further element includes a present value ofthe second premium payment stream.

A fourth sub-step to analyze the subsets of the multitude of availablelongevity-contingent instruments includes aggregating the firstcharacterization information and the second characterization informationto produce the characterization information 720. The characterizationinformation 720 further includes insured age, gender, smoker, insuredhealth record, historical life expectancy data, a requested purchaseprice, an offered purchase price, etc.).

Having analyzed the multitude of available longevity-contingentinstruments to produce the characterization information 720, in a fourthstep, when the first characterization information and the secondcharacterization information compare favorably to the rive approachrequirements 714, the processing module 44 selects the firstlongevity-contingent instrument 722 and the second longevity-contingentinstrument 724 to include in the set of longevity-contingentinstruments. For example, the processing module 44 identifies the firstand second longevity-contingent instruments, causes title transfer(e.g., purchase via a transaction with the user device 32-1 and/orlongevity-contingent instrument provider servers 704-1), and lists thefirst and second longevity-contingent instruments in thelongevity-contingent instrument information 660 of the database 30.

FIG. 13C further illustrates the example of the riving of thelongevity-contingent instruments where, having selected thelongevity-contingent instruments, in a fifth step, the processing module44 rives the first longevity-contingent instrument 722 based on thefirst face value benefit, the first premium payment stream and inaccordance with the rive approach 682 to produce a first sub-asset 728of a plurality of sub-assets of the set of longevity-contingentinstruments and a first sub-liability 730 of a plurality ofsub-liabilities of the set of longevity-contingent instruments. Thefirst sub-liability 730 is associated with the first premium paymentstream.

The riving of the first longevity-contingent instrument 722 includesgenerating beneficiary ownership of the first face value benefit to beassociated with the first sub-asset 728. For example, the processingmodule 44 facilitates listing a legal entity of the first sub-asset as apartial beneficiary of the first longevity-contingent instrument andupdates the sub-asset information 690 with the first sub-asset 728. Asanother example, the processing module 44 facilitates listing anotherlegal entity of the first sub-liability as one of another partialbeneficiary of the first longevity-contingent instrument and updates thesub-liability information 726 with the first sub-liability 730.

The riving of the first longevity-contingent instrument 722 furtherincludes generating fiduciary responsibility of the first premiumpayment stream to be associated with the first sub-liability. Forexample, the processing module 44 facilitates listing the other legalentity of the first sub-liability as having fiduciary responsibility ofthe first premium payment stream of the first longevity-contingentinstrument 722.

Having rived the first longevity-contingent instrument 722, in a sixthstep, the processing module 44 rives the second longevity-contingentinstrument 724 based on the second face value benefit, the secondpremium payment stream and in accordance with the rive approach 682 toproduce a second sub-asset 732 of the plurality of sub-assets and asecond sub-liability 734 of the plurality of sub-liabilities. The secondsub-liability 734 is associated with the second premium payment stream.The processing module 44 further updates the sub-asset information 690with the second sub-asset 732 and updates the sub-liability information726 with the second sub-liability 734.

FIG. 13D further illustrates the example of the riving of thelongevity-contingent instruments where, having rived thelongevity-contingent instruments, in a seventh step, the processingmodule 44 issues sub-asset information 690 to the benefactor computingdevice (e.g., to the benefactor server 700). The sub-asset information690 is based on the plurality of sub-assets and the rive approach 682.The issuing includes generating the sub-asset information 690 from allof the sub-assets and sending, via the network 28 of FIG. 1 , thesub-asset information 690 to the benefactor server 700.

Having issued the sub-asset information, in an eight step, theprocessing module 44 issues sub-liability information 726 to the debtorcomputing device (e.g., to the debtor server 702). The sub-liabilityinformation 726 is based on the plurality of sub-liabilities and therive approach 682. The issuing includes generating the sub-liabilityinformation 726 from all of the sub-liabilities and sending, via thenetwork 28 of FIG. 1 , the sub-liability information 726 to the debtorserver 702.

FIG. 13E further illustrates the example of the riving of thelongevity-contingent instruments where, having issued the sub-liabilityinformation to the debtor computing device, in a ninth step, theprocessing module 44 associates the plurality of sub-assets with abenefit cash account 670 and associates the plurality of sub-liabilitieswith a premium cash escrow 668. The benefit cash account 670 isassociated with the benefactor computing device and the premium cashescrow 668 is associated with the debtor computing device.

Having associated the sub-assets and the sub-liabilities, in a tenthstep, the processing module 44, when available (e.g., upon payment of adeath benefit), facilitates payment of a first portion of the first facevalue benefit 742 to the premium cash escrow 668 in accordance with thefirst sub-liability. The first portion of the first face value benefitis determined in accordance with the rive approach 682. The tenth stepfurther includes the processing module 44, when available, facilitatingpayment of a second portion of the first face value benefit 744 to thebenefit cash account 670 in accordance with the first sub-asset. Thesecond portion of the first face value benefit is determined inaccordance with the rive approach 682 and the first portion of the firstface value benefit. Alternatively, or in addition to, the processingmodule 44 facilitates payment of a portion of the second premium paymentstream utilizing one or more of the premium cash escrow 668 and apremium offset from the debtor computing device.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 14A-14E are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forgenerating a portfolio of blockchain-encoded rived longevity-contingentinstruments within a computing system. The computing system includes abenefactor server 700, a debtor server 702, user devices 32-1 through32-N, longevity-contingent instrument provider servers 704-1 through704-M, and the control server 20 of FIG. 1 .

In an embodiment, the benefactor server 700 and the debtor server 702are implemented utilizing the legacy server 22 of FIG. 1 , where thebenefactor server 700 is associated with at least one benefit entity(e.g., pension system) and the debtor server 702 is associated with atleast one sponsor entity associated with the at least one benefitentity. In an embodiment, the user devices 32-1 through 32-N areimplemented utilizing the user devices 32 of FIG. 1 . In an embodiment,the longevity-contingent instrument provider servers 704-1 through 704-Mare implemented utilizing the augmentation server 24 of FIG. 1 . Thecontrol server 20 includes the processing module 44 of FIG. 1 and thedatabase 30 of FIG. 1 .

FIG. 14A illustrates an example of operation of steps of a method forthe generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, in a first step, the processingmodule 44 interprets digitally encoded rive parameters from one or moreof a benefactor computing device (e.g., the benefactor server 700) and adebtor computing device (e.g., the debtor server 702) to produce riveapproach requirements 714. The interpreting includes a series of one ormore operations. A first operation includes decrypting encrypted assetrive parameters 752 received from the benefactor server 700 to produce afirst subset of the digitally encoded rive parameters. A secondoperation includes decoding the first subset of the digitally encodedrive parameters to produce asset rive parameters.

A third operation includes decrypting encrypted liability riveparameters 754 received from the debtor server 702 to produce a secondsubset of the digitally encoded rive parameters. A fourth operationincludes decoding the second subset of the digitally encoded riveparameters to produce liability rive parameters. A fifth operationincludes aggregating the asset rive parameters and the liability riveparameters to produce the rive approach requirements 714.

Having produced the rive approach requirements 714, in a second step ofthe method for the generating of the portfolio of blockchain-encodedrived longevity-contingent instruments, the processing module 44 obtainsa rive approach 682 for riving a set of longevity-contingent instrumentsof a multitude of available longevity-contingent instruments based onthe rive approach requirements 714. A first longevity-contingentinstrument of the set of longevity-contingent instruments includes afirst face value benefit and a first premium payment stream. The firstlongevity-contingent instrument assigns the first face value benefit andthe first premium payment stream to a first ownership entity (e.g.,originally insured or a broker/holding entity).

A second longevity-contingent instrument of the set oflongevity-contingent instruments includes a second face value benefitand a second premium payment stream. The second longevity-contingentinstrument assigns the second face value benefit and the second premiumpayment stream to a second ownership entity (e.g., another originallyinsured or the broker/holding entity). In an embodiment, when an insuredperson passes and a death benefit is provided, availability of a firstportion of the first face value benefit is utilized to fund at leastsome of the second premium payment stream in accordance with the riveapproach 682.

The obtaining of the rive approach 682 includes determining, retrieving,and receiving. For example, the processing module 44 determines the riveapproach 682 based on the rive approach requirements 714 as previouslydiscussed. As another example, the processing module 44 retrieves therive approach requirements 714 from the database 30. As yet anotherexample, the processing module 44 receives the rive approachrequirements 714 from another computing device.

FIG. 14B further illustrates the example of operation of steps of themethod for the generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having obtained the riveapproach 682, in a third step, the processing module 44 verifiesauthenticity of a group of blockchain-encoded records 800 representing asubset of the multitude of available longevity-contingent instruments toproduce an authenticity indicator 806. The subset of the multitude ofavailable longevity-contingent instruments includes the firstlongevity-contingent instrument 722 and the second longevity-contingentinstrument 724.

The verifying of the authenticity includes obtaining the group ofblockchain-encoded records 800 and analyzing the group ofblockchain-encoded records 800 for authenticity. The obtaining of thegroup of blockchain-encoded records 800 includes accessing one or bothof a primary market and a secondary market. Accessing the primary marketincludes obtaining blockchain-encoded records for longevity-contingentinstruments directly from initial policyholders (e.g., originallyinsured individuals). Accessing the secondary market includes obtainingfurther blockchain-encoded records for further longevity-contingentinstruments from brokers and providers, where the blockchain-encodedrecords of longevity-contingent instruments have changed hands from theinitial policyholders to one or more intermediaries (e.g., the brokers,etc.).

The accessing of the blockchain-encoded records 800 includes a series ofsub-steps. A first sub-step includes identifying the multitude ofavailable longevity-contingent instruments by one or more of issuing asolicitation message for longevity-contingent instrument information andreceiving the longevity-contingent instrument information. For example,the processing module 44 issues a solicitation message to one or more ofthe user devices 32-1 through 32-N, and in response, receives primarymarket blockchain-encoded records 802. As another example, theprocessing module 44 issues the solicitation message to one or more ofthe longevity-contingent instrument provider servers 704-1 through704-M, and in response, receives at least one of secondary marketblockchain-encoded records 804-1 through 804-M. Alternatively, theprocessing module 44 receives the blockchain-encoded records 800 in anunsolicited fashion.

The analyzing of the group of blockchain-encoded records 800 forauthenticity includes utilizing a symmetric key signature approach oranother approach including a straightforward signature verification.When utilizing the symmetric key signature approach, the processingmodule 44 decrypts a first signature of a first blockchain-encodedrecord of the blockchain-encoded records 800 utilizing a first publickey of a first public-private key pair to produce a first decryptedtransaction hash value. The first public-private key pair is associatedwith a last transaction computing device (e.g., a computing deviceassociated with a last transfer of ownership of the associatedlongevity-contingent instrument).

Having produced the first decrypted transaction hash value, theprocessing module 44 hashes a portion of the first blockchain-encodedrecord utilizing a second public key of a second public-private key pairto produce a candidate transaction hash value. The second public-privatekey pair is associated with the computing device (e.g., generated by thecomputing device). Having produced the candidate transaction hash value,the processing module 44 establishes the authenticity indicator 806 toindicate favorable authenticity when the first decrypted transactionhash value compares favorably to the candidate transaction hash value.

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the first signature of thefirst blockchain-encoded record utilizing the first public key and thesecond public key to produce the authenticity indicator. Theauthentication is discussed in greater detail with reference to FIG.14C.

FIG. 14C further illustrates the example of operation of steps of themethod for the generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, blockchain-encoded records areutilized to securely represent longevity-contingent instruments. Inparticular, a blockchain of blockchain-encoded records is utilized torecord transactions and updates associated with a particularlongevity-contingent instrument. For instance, a new blockchain iscreated when a life insurance policy is initially created by anassociated insurance provider and sold to the originally insured. Asanother instance, the blockchain is updated when the life insurancepolicy is sold by the originally insured in the primary market to asecond owner. As yet another instance, the blockchain is updated whenlife insurance policy is sold by the second owner to a third owner.

Each block of the blockchain includes various fields associated with theblockchain and a transaction field that includes content associated withthe corresponding life insurance policy. The content includes one ormore of insured name, a longevity status (e.g., living, deceased),policy terms (e.g., initial purchase price, death benefit, premiumpayment information), insured health records, an estimated lifeexpectancy, a net present value, a current owner, a current holder(e.g., a fiduciary associated with the current owner), and insurancecompany information. Further information is included as is discussedwith reference to FIG. 14D.

The example blockchain includes blocks 2-4. Each block includes a headersection and a transaction section. The header section includes one ormore of a nonce, a hash of a preceding block of the blockchain, wherethe preceding block was under control of a preceding computing device(e.g., a computing device of a seller) in a chain of control of theblockchain, and a hash of a current block (e.g., a current transactionsection). The current block is under control of a current computingdevice in the chain of control of the blockchain.

The transaction section includes one or more of a public key of thecurrent computing device, a signature of the preceding computing device,request information regarding a record request and change of controlfrom the preceding computing device to the current computing device, andcontent information from the previous block as received by the previouscomputing device plus content added by the previous computing devicewhen transferring the current block to the current computing device.

The example further includes computing devices 2-3 (e.g., devices #2 and#3) to facilitate illustration of generation of the blockchain. Eachcomputing device includes a hash function, a signature function, andstorage for a public/private key pair generated by the device.

An example of operation of the generating of the blockchain, when thedevice 2 has control of the blockchain and is passing control of theblockchain to the device 3 (e.g., the device 3 is transacting a transferof content from device 2), the device 2 obtains the device 3 public keyfrom device 3, performs a hash function 2 over the device 3 public keyand the transaction 2 to produce a hashing resultant (e.g., precedingtransaction to device 2) and performs a signature function 2 over thehashing resultant utilizing a device 2 private key to produce a device 2signature.

Having produced the device 2 signature, the device 2 generates thetransaction 3 to include the device 3 public key, the device 2signature, device 3 record request to device 2 information, and theprevious content plus content from device 2. The device 3 record requestto device 2 information includes one or more of the actual recordrequest, a query request, background content, and routing instructionsfrom device 3 to device 2 for access to the content. The previouscontent plus content from device 2 includes one or more of content froman original source, content from any subsequent source after theoriginal source, an identifier of a source of content, a serial numberof the content, an expiration date of the content, content utilizationrules, and results of previous blockchain validations.

Having produced the transaction 3 section of the block 3 a processingmodule (e.g., of the device 2, of the device 3, of a transaction miningcomputing entity, of a computing device), generates the header sectionby performing a hashing function over the transaction section 3 toproduce a transaction 3 hash, performing the hashing function over thepreceding block (e.g., block 2) to produce a block 2 hash. Theperforming of the hashing function may include generating a nonce suchthat when performing the hashing function to include the nonce of theheader section, a desired characteristic of the resulting hash isachieved (e.g., a desired number of zero's).

Having produced the block 3, the device 2 sends the block 3 to thedevice 3, where the device 3 initiates control of the blockchain. Havingreceived the block 3, the device 3 validates the received block 3. Thevalidating includes one or more of verifying the device 2 signature overthe preceding transaction section (e.g., transaction 2) and the device 3public key utilizing the device 2 public key (e.g., a re-createdsignature function result compares favorably to device 2 signature) andverifying that an extracted device 3 public key of the transaction 3compares favorably to the device 3 public key held by the device 3. Thedevice 3 considers the received block 3 validated when the verificationsare favorable (e.g., the authenticity of the associated content istrusted). For instance, the device considers the records intact, valid,and usable to facilitate determination of selection for the set oflongevity-contingent instruments.

FIG. 14D further illustrates the example of operation of steps of themethod for the generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having produce the authenticityindicator 806, in a fourth step, when the authenticity indicator for thegroup of blockchain-encoded records is favorable (e.g., authentic), theprocessing module 44 selects the first longevity-contingent instrument722 and the second longevity-contingent instrument 724 based on the riveapproach 682 to include in a set of longevity-contingent instruments(e.g., the portfolio). The set of longevity-contingent instruments isassociated with a fair market acquisition value (e.g., purchase pricebased on current status where a common ownership entity owns both theface value benefit and the premium payment stream). The selectingincludes a series of sub-steps. The processing module maintains recordsof the plurality of longevity-contingent instruments aslongevity-contingent instrument information 660 within the database 30.

A first sub-step of the series of sub-steps includes extracting firstcharacterization information 808 from the first blockchain-encodedrecord for the first longevity-contingent instrument to include one ormore of a first estimated timeframe for payout of the first face valuebenefit, a present value of the first face value benefit utilizing thefirst estimated timeframe, and a present value of the first premiumpayment stream. A second sub-step includes extracting secondcharacterization information 810 from the second blockchain-encodedrecord for the second longevity-contingent instrument to include one ormore of a second estimated timeframe for payout of the second face valuebenefit, a present value of the second face value benefit utilizing thesecond estimated timeframe, and a present value of the second premiumpayment stream.

A third sub-step includes selecting the first longevity-contingentinstrument 722 and the second longevity-contingent instrument 724 toinclude in the set of longevity-contingent instruments when the firstcharacterization information 808 and the second characterizationinformation 810 compare favorably to the rive approach requirements 714associated with the rive approach 682. For example, the first and secondlongevity-contingent instruments provide an estimated favorable outcomealigned with the rive approach requirements 714.

Having selected the first and second longevity-contingent instruments,in a fifth step of the method for the generating of the portfolio ofblockchain-encoded rived longevity-contingent instruments, theprocessing module 44 generates selection information 812 for subsequentupdating of the blockchain-encoded records 800 (e.g., to documenttransfer of ownership and a payment amount). The selection informationis generated to include one or more of an identifier of a benefactorcomputing device associated with the benefit entity, an identifier of adebtor computing device associated with the sponsor entity, anidentifier of an associated blockchain-encoded record, an identifier ofan associated longevity-contingent instrument, a current purchasetransaction value, an ownership entity identifier, a holder identifier,an updated life expectancy value, an updated longevity status indicator,and an identifier of another longevity-contingent instrument of the setof longevity-contingent instruments.

FIG. 14E further illustrates the example of operation of steps of themethod for the generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having generated the selectioninformation 812, in a sixth step, the processing module 44 updates thefirst blockchain-encoded record for the first longevity-contingentinstrument 722 and a second blockchain-encoded record for the secondlongevity-contingent instrument 724 to include the selection information812. The group of blockchain-encoded records 800 includes the first andsecond blockchain-encoded records. The processing module maintainsrecords of the plurality of longevity-contingent instruments aslongevity-contingent instrument information 660 within the database 30.

The updating of a blockchain-encoded record includes a series ofsub-steps. In a first sub-step the processing module 44 hashes theselection information 812 utilizing a recipient public key of arecipient computing device to produce a next transaction hash value. Ina second sub-step the processing module 44 encrypts the next transactionhash value utilizing a private key of the computing device to produce anext transaction signature. In a third sub-step the processing module 44generates a next blockchain-encoded record to include the selectioninformation 812 and the next transaction signature.

Having updated the blockchain-encoded records, in a seventh step of themethod for the generating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments, the processing module 44 rives thefirst and second longevity-contingent instruments in accordance with therive approach 682 to produce sub-assets and sub-liabilities. Forexample, the processing module 44 rives the first longevity-contingentinstrument 722 in accordance with the rive approach 682 to reassign thefirst face value benefit from the first ownership entity to the benefitentity to produce a first sub-asset 728 of a plurality of sub-assets ofthe set of longevity-contingent instruments. As another example, theprocessing module 44 further rives the first longevity-contingentinstrument 722 in accordance with the rive approach 682 to reassign thefirst premium payment stream from the first ownership entity to thesponsor entity to produce a first sub-liability 730 of a plurality ofsub-liabilities of the set of longevity-contingent instruments.

The plurality of sub-assets is associated with a benefit net presentvalue and the plurality of sub-liabilities is associated with aliability net present value. A beneficial valuation elevation is createdsuch that a sum of the benefit net present value and the liability netpresent value is greater than the fair market acquisition value so thatthe benefit entity and sponsor entity realize the beneficial valuationelevation over direct utilization of selected longevity-contingentinstruments of the set of longevity-contingent instruments prior to theriving.

As yet another example of the riving, the processing module 44 rives thesecond longevity-contingent instrument 724 in accordance with the riveapproach 682 to reassign the second face value benefit from the secondownership entity to the benefit entity to produce a second sub-asset 732of the plurality of sub-assets of the set of longevity-contingentinstruments. The processing module 44 further rives the secondlongevity-contingent instrument 724 in accordance with the rive approach682 to reassign the second premium payment stream from the secondownership entity to the sponsor entity to produce a second sub-liability734 of the plurality of sub-liabilities of the set oflongevity-contingent instruments. Having produced the plurality ofsub-assets and the plurality of sub-liabilities, the processing module44 stores the sub-assets and the plurality of sub-liabilities assub-asset information 690 and sub-liability information 726 in thedatabase 30.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 15A-15C are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forutilizing a portfolio of blockchain-encoded rived longevity-contingentinstruments within a computing system. The computing system includesdata sources 26-1 through 26-N, a payer computing device 850, thetransactional server 18 of FIG. 1 , a benefactor computing device 852,and a debtor computing device 854.

In an embodiment, the payer computing device 850 is implementedutilizing the augmentation server 24 FIG. 1 . In an embodiment, thebenefactor computing device 852 and the debtor computing device 854 areimplemented utilizing legacy server 22 of FIG. 1 . In an embodiment, thedata sources 26-1 through 26-N are implemented utilizing the data source26 of FIG. 1 . The transactional server 18 includes the processingmodule 44 of FIG. 1 and the database 30 of FIG. 1 .

FIG. 15A illustrates an example of operation of steps of a method forthe utilizing of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, in a first step, the processingmodule 44 obtains a first blockchain-encoded record 864 representing afirst longevity-contingent instrument 722. When an insured person passesand a death benefit is provided, availability of a benefit payout isutilized to fund a combination of a cash flow to the benefactorcomputing device 852, for a benefit entity, and for at least some of aplurality of premium payment streams on behalf of the debtor computingdevice 854, of a sponsor entity, from the payer computing device 850 inaccordance with a rive approach 682. The first blockchain-encoded record864 includes a notification of the death benefit.

The obtaining includes receiving one or more blockchain-encoded records860-1 through 860-N from one or more of the data sources 26-1 through26-N. The obtaining further includes receiving a blockchain-encodedrecord 862 from the payer computing device 850 when the payer computingdevice 850 issues the notification of the death benefit (e.g., the lifeinsurance company issues the notice).

Having obtained the first blockchain-encoded record representing thefirst longevity-contingent instrument 722, a second step of the methodfor the utilizing of the portfolio of blockchain-encoded rivedlongevity-contingent instruments includes the processing module 44verifying authenticity of the first blockchain-encoded record 864representing the first longevity-contingent instrument 722 of aportfolio of longevity-contingent instruments to produce a verifiedfirst blockchain-encoded record. The processing module maintains recordsof the portfolio of longevity-contingent instruments aslongevity-contingent instrument information 660 within the database 30.The portfolio of longevity-contingent instruments is associated with afair market acquisition value.

The first longevity-contingent instrument 722 is selected and rived inaccordance with a rive approach 682 to reassign a first face valuebenefit from a first ownership entity to the benefit entity to produce afirst sub-asset (e.g., death benefit) of a plurality of sub-assets ofthe portfolio of longevity-contingent instruments. The firstlongevity-contingent instrument 722 is further selected and rived inaccordance with the rive approach 682 to reassign a first premiumpayment stream from the first ownership entity to the sponsor entity toproduce a first sub-liability of a plurality of sub-liabilities of theportfolio of longevity-contingent instruments.

The plurality of sub-assets is associated with a benefit net presentvalue and the plurality of sub-liabilities is associated with aliability net present value. The selecting and riving creates abeneficial valuation elevation such that a sum of the benefit netpresent value and the liability net present value is greater than thefair market acquisition value.

The verifying of the authenticity includes utilizing a symmetric keysignature approach or another approach (e.g., straightforward signatureverification). When utilizing the symmetric key signature approach, theprocessing module 44 decrypts a first signature of the firstblockchain-encoded record 864 utilizing a first public key of a firstpublic-private key pair to produce a first decrypted transaction hashvalue. The first public-private key pair is associated with a lasttransaction computing device (e.g., a computing device associated withgenerating the death notification).

Having produced the first decrypted transaction hash value, theprocessing module 44 hashes a portion of the first blockchain-encodedrecord utilizing a second public key of a second public-private key pairto produce a candidate transaction hash value. The second public-privatekey pair is associated with the computing device (e.g., generated by thecomputing device). Having produced the candidate transaction hash value,the processing module 44 indicates favorable authenticity when the firstdecrypted transaction hash value compares favorably to the candidatetransaction hash value.

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the first signature of thefirst blockchain-encoded record utilizing the first public key and thesecond public key to produce the authenticity indicator. The verifyingof the authenticity was previously discussed in greater detail withreference to FIG. 14C.

FIG. 15B further illustrates the example of operation of steps of themethod for the utilizing of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having verify the authenticityof the first blockchain-encoded record 864, in a third step, theprocessing module 44 determines that the first longevity-contingentinstrument 722 is associated with an available and unfulfilled benefitstatus by at least one of several approaches.

A first approach includes interpreting the first longevity-contingentinstrument 722 to identify a first death-notification of a first insuredperson identifier. The first insured person identifier is associatedwith the first longevity-contingent instrument 722. A second approachincludes interpreting the first longevity-contingent instrument 722 toidentify the unfulfilled benefit status of the firstlongevity-contingent instrument 722. A third approach includes accessingthe longevity-contingent instrument information 660 from the database 30to extract a plurality of insured person identifiers of the plurality oflongevity-contingent instruments and identifying the first insuredperson identifier within the plurality of insured person identifiers.

Having determined that the first longevity-contingent instrument 722 isassociated with the available and unfulfilled benefit status, a fourthstep of the method for utilizing of the portfolio of blockchain-encodedrived longevity-contingent instruments includes the processing module 44determining fulfillment information 866 for the firstlongevity-contingent instrument 722. The fulfillment information 866includes a benefit payout 868 of the first sub-asset facilitated by thepayer computing device 850 for the benefit entity.

The fulfillment information 866 includes a variety of one or moreelements. The elements include an identifier of the computing device, anidentifier of the benefactor computing device 852 associated with thebenefit entity, an identifier of the debtor computing device 854associated with the sponsor entity, and an identifier of the payercomputing device 850. The elements of the fulfillment information 866further includes a request for the payment of the benefit payout 868, acurrent purchase transaction value, the benefit payout 868, and afulfillment status of the benefit payout 868.

The elements of the fulfillment information 866 further includes anownership entity identifier, a holder identifier, an insured personidentifier, an identifier of an associated blockchain-encoded record, anidentifier of an associated longevity-contingent instrument, a healthrecord, and an updated life expectancy value. The elements of thefulfillment information 866 further includes a death-notification of theinsured person identifier, an updated longevity status indicator, and anidentifier of another longevity-contingent instrument associated withthe first longevity-contingent instrument 722.

The determining of the fulfillment information 866 includes at least oneof a variety of approaches. A first approach includes determining thebenefit payout associated with the first sub-asset. A second approachincludes generating a request for the payment of the benefit payout. Athird approach includes determining a first portion of the benefitpayout to associate with a premium cash escrow in accordance with therive approach 682. The premium cash escrow is utilized to fund paymentof a plurality of premium payment streams associated with the pluralityof sub-liabilities of the portfolio of longevity-contingent instrumentson behalf of the sponsor entity.

A third approach includes determining a second portion of the benefitpayout to associate with a benefit cash account based on the firstportion of the payout and in accordance with the rive approach 682. Thebenefit cash account is associated with the benefit entity (e.g., one ormore benefactors) associated with the benefactor computing device 852.

FIG. 15C further illustrates the example of operation of steps of themethod for the utilizing of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having produce the fulfillmentinformation 866, in a fifth step, the processing module 44 updates thefirst blockchain-encoded record 864 for the first longevity-contingentinstrument 722 based on security information (e.g., key pairinformation) of the payer computing device 850 to include thefulfillment information 866 to produce an updated firstblockchain-encoded record 872.

The updating of the first blockchain-encoded record 864 includes aseries of sub-steps. In a first sub-step the processing module 44 hashesthe fulfillment information 866 utilizing a recipient public key of arecipient computing device (e.g., of the payer computing device 850) toproduce a next transaction hash value. In a second sub-step theprocessing module 44 encrypts the next transaction hash value utilizinga private key of the computing device to produce a next transactionsignature. In a third sub-step the processing module 44 generates a nextblockchain-encoded record to include the fulfillment information 866 andthe next transaction signature.

Having produced the updated first blockchain-encoded record 872, in asixth step of the method of the utilizing of the portfolio ofblockchain-encoded rived longevity-contingent instruments, theprocessing module 44 sends the updated first blockchain-encoded record872 to the payer computing device 850 to facilitate payment of thebenefit payout 868 of the first sub-asset to the benefit entity. Thebenefit entity and sponsor entity realize the beneficial valuationelevation over direct utilization of selected longevity-contingentinstruments of the portfolio of longevity-contingent instruments priorto the riving. The facilitating of the payment includes generating astill further updated representation of the first blockchain-encodedrecord to include confirmation of payment.

Alternatively, or in addition to, the processing module 44 sends arepresentation of the updated first blockchain-encoded record 872 to oneor more of the benefactor computing device 852 and the debtor computingdevice 854. For instance, the processing module 44 further updates theupdated first blockchain-encoded record 872 based on securityinformation of at least one of the benefactor computing device 852 andthe debtor computing device 854 to include the fulfillment information866 to produce a further updated first blockchain-encoded record as therepresentation of the updated first blockchain-encoded record. Havingproduced the representation, the processing module 44 sends therepresentation as one or more of an updated first blockchain-encodedrecord 874 to the benefactor computing device 852 and as an updatedfirst blockchain-encoded record 876 to the debtor computing device 854.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 16A-16D are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method for updatinga portfolio of blockchain-encoded rived longevity-contingent instrumentswithin a computing system. The computing system includes a benefactorserver 700, a debtor server 702, user devices 32-1 through 32-N,longevity-contingent instrument provider servers 704-1 through 704-M,and the control server 20 of FIG. 1 .

In an embodiment, the benefactor server 700 and the debtor server 702are implemented utilizing the legacy server 22 of FIG. 1 , where thebenefactor server 700 is associated with at least one benefit entity(e.g., pension system) and the debtor server 702 is associated with atleast one sponsor entity associated with the at least one benefitentity. In an embodiment, the user devices 32-1 through 32-N areimplemented utilizing the user devices 32 of FIG. 1 . In an embodiment,the longevity-contingent instrument provider servers 704-1 through 704-Mare implemented utilizing the augmentation server 24 of FIG. 1 . Thecontrol server 20 includes the processing module 44 of FIG. 1 and thedatabase 30 of FIG. 1 .

FIG. 16A illustrates an example of operation of steps of a method forthe updating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, in a first step, the processingmodule 44 determines to update a set of longevity-contingent instruments(e.g., an existing portfolio of blockchain-encoded rivedlongevity-contingent instruments). A first longevity-contingentinstrument of the set of longevity-contingent instruments is rived inaccordance with a rive approach 682 to reassign a first face valuebenefit of the first longevity-contingent instrument from a firstownership entity (e.g., originally insured or a broker/holding entity)to a benefit entity to produce a first sub-asset of a plurality ofsub-assets of the set of longevity-contingent instruments.

The first longevity-contingent instrument is further rived in accordancewith the rive approach 682 to reassign a first premium payment stream ofthe first longevity-contingent instrument from the first ownershipentity to a sponsor entity to produce a first sub-liability of aplurality of sub-liabilities of the set of longevity-contingentinstruments. The plurality of sub-assets is associated with a benefitnet present value and the plurality of sub-liabilities is associatedwith a liability net present value. The control server 20 maintainsinformation with regards to the set of longevity-contingent instruments,including the first longevity-contingent instrument, in the database 30.The control server 20 further maintains information with regards to theplurality of sub-assets as sub-asset information 690 and informationwith regards to the plurality of sub-liabilities as sub-liabilityinformation 726 in the database 30.

The processing module 44 determines to update the set oflongevity-contingent instruments utilizing one or more of a variety ofapproaches. A first approach includes interpreting a request. Forexample, the processing module 44 interprets a request to update the setof longevity-contingent instruments 878 received from one or more of thebenefactor server 700 and the debtor server 702.

A second approach includes determining to add anotherlongevity-contingent instrument to the set of longevity-contingentinstruments. For example, the processing module 44 determines to expandthe portfolio of blockchain-encoded rived longevity-contingentinstruments by adding (e.g., buying) the other longevity-contingentinstrument to the set of longevity-contingent instruments.

A third approach includes determining to remove an existinglongevity-contingent instrument from the set of longevity-contingentinstruments. For example, the processing module determines to contractthe portfolio of blockchain-encoded rived longevity-contingentinstruments by removing (e.g., selling) the existinglongevity-contingent instrument from the set of longevity-contingentinstruments.

A fourth approach to update the set of longevity-contingent instrumentsincludes determining that a sum of the benefit net present value and theliability net present value associated with the set oflongevity-contingent instruments is less than a low threshold. Forexample, the processing module 44 determines each of the benefit netpresent value and the liability net present value of valuationinformation 880 and compares the sum of the two to the low threshold.When the sum is less than the low threshold, the processing module 44indicates to update the set of longevity-contingent instruments (e. g.,buying).

FIG. 16B further illustrates the example of operation of steps of themethod for the updating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having determined to update theset of longevity-contingent instruments, in a second step, theprocessing module 44 verifies authenticity of a blockchain-encodedrecord 882 representing a second longevity-contingent instrument 724 toproduce an authenticity indicator 806. The second longevity-contingentinstrument assigns a second face value benefit of the secondlongevity-contingent instrument and a second premium payment stream ofthe second longevity-contingent instrument to a second ownership entity(e.g., another originally insured or the broker/holding entity).

The verifying of the authenticity includes obtaining theblockchain-encoded record 882 and analyzing the record for authenticity.The obtaining of the blockchain-encoded record 882 includes accessingone or both of a primary market and a secondary market. Accessing theprimary market includes obtaining one or more blockchain-encoded recordsfor longevity-contingent instruments directly from initial policyholders(e.g., originally insured individuals). Accessing the secondary marketincludes obtaining one or more further blockchain-encoded records forfurther longevity-contingent instruments from brokers and providers,where the blockchain-encoded records of longevity-contingent instrumentshave changed hands from the initial policyholders to one or moreintermediaries (e.g., the brokers, etc.).

The accessing of the blockchain-encoded record 882 includes a series ofsub-steps. A first sub-step includes identifying one or more availablelongevity-contingent instruments by one or more of issuing asolicitation message for longevity-contingent instrument information andreceiving the longevity-contingent instrument information. For example,the processing module 44 issues a solicitation message to one or more ofthe user devices 32-1 through 32-N, and in response, receives primarymarket blockchain-encoded records 802. As another example, theprocessing module 44 issues the solicitation message to one or more ofthe longevity-contingent instrument provider servers 704-1 through704-M, and in response, receives at least one of secondary marketblockchain-encoded records 804-1 through 804-M. Alternatively, theprocessing module 44 receives the blockchain-encoded record 882 in anunsolicited fashion.

The analyzing of the blockchain-encoded record 882 for authenticityincludes utilizing a symmetric key signature approach or anotherapproach including a straightforward signature verification. Whenutilizing the symmetric key signature approach, the processing module 44decrypts a signature of a first blockchain-encoded record of theblockchain-encoded record 882 utilizing a first public key of a firstpublic-private key pair to produce a first decrypted transaction hashvalue. The first public-private key pair is associated with a lasttransaction computing device (e.g., a computing device associated with alast transfer of ownership of an associated longevity-contingentinstrument).

Having produced the first decrypted transaction hash value, theprocessing module 44 hashes a portion of the blockchain-encoded recordutilizing a second public key of a second public-private key pair toproduce a candidate transaction hash value. The second public-privatekey pair is associated with the computing device (e.g., generated by thecomputing device). Having produced the candidate transaction hash value,the processing module 44 establishes the authenticity indicator 806 toindicate favorable authenticity when the first decrypted transactionhash value compares favorably to the candidate transaction hash value(e.g., substantially the same).

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the signature of theblockchain-encoded record utilizing the first public key and the secondpublic key to produce the authenticity indicator 806. The authenticationwas discussed in greater detail with reference to FIG. 14C.

FIG. 16C further illustrates the example of operation of steps of themethod for the updating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having verified the authenticityof the blockchain-encoded record 882 to produce the authenticityindicator 806, in a third step, when the authenticity indicator for theblockchain-encoded record is favorable (e.g., authentic), the processingmodule 44 determines to include the second longevity-contingentinstrument 724 in the set of longevity-contingent instruments to producean updated set of longevity-contingent instruments. The updated set oflongevity-contingent instruments is associated with a fair marketacquisition value (e.g., purchase price based on current status where acommon ownership entity owns both the face value benefit and the premiumpayment stream).

The determining to include the second longevity-contingent instrument724 in the set of longevity-contingent instruments to produce theupdated set of longevity-contingent instruments includes a series ofsub-steps. A first sub-step includes extracting characterizationinformation 884 from the blockchain-encoded record 882 for the secondlongevity-contingent instrument 724 to include one or more of anestimated timeframe for payout of the second face value benefit, apresent value of the second face value benefit utilizing the estimatedtimeframe, and a present value of the second premium payment stream.

A second sub-step includes indicating to include the secondlongevity-contingent instrument 724 in the set of longevity-contingentinstruments to produce the updated set of longevity-contingentinstruments when the characterization information 884 compares favorablyto rive approach requirements 714 associated with the rive approach 682.For example, the second longevity-contingent instrument 724 provides anestimated favorable outcome aligned with the rive approach requirements714.

Having determined to produce the updated set of longevity-contingentinstruments, in a fourth step of the method for the updating of theportfolio of blockchain-encoded rived longevity-contingent instruments,the processing module 44 generates selection information 812 forsubsequent updating of the blockchain-encoded records 800 (e.g., todocument transfer of ownership and a payment amount). The selectioninformation is generated to include one or more of an identifier of abenefactor computing device associated with the benefit entity, anidentifier of a debtor computing device associated with the sponsorentity, an identifier of an associated blockchain-encoded record, anidentifier of an associated longevity-contingent instrument, a currentpurchase transaction value, an ownership entity identifier, a holderidentifier, an updated life expectancy value, an updated longevitystatus indicator, and an identifier of another longevity-contingentinstrument of the set of longevity-contingent instruments.

FIG. 16D further illustrates the example of operation of steps of themethod for the updating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments where, having produced the selectioninformation 812, in a fifth step, the processing module 44 updates theblockchain-encoded record 882 for the second longevity-contingentinstrument to include the selection information 812. The updating of theblockchain-encoded record 882 includes a series of sub-steps. In a firstsub-step, the processing module 44 hashes the selection information 812utilizing a recipient public key of a recipient computing device toproduce a next transaction hash value. In a second sub-step, theprocessing module 44 encrypts the next transaction hash value utilizinga private key of the computing device to produce a next transactionsignature. In a third sub-step, the processing module 44 generates anext blockchain-encoded record to include the selection information 812and the next transaction signature.

Having updated the blockchain-encoded record 882, in a sixth step of themethod for the updating of the portfolio of blockchain-encoded rivedlongevity-contingent instruments, the processing module 44 rives thesecond longevity-contingent instrument 724 in accordance with the riveapproach 682 to reassign the second face value benefit from the secondownership entity to the benefit entity to produce a second sub-asset 732of the plurality of sub-assets of the updated set oflongevity-contingent instruments, and to reassign the second premiumpayment stream from the second ownership entity to the sponsor entity toproduce a second sub-liability 734 of the plurality of sub-liabilitiesof the updated set of longevity-contingent instruments.

Having produced the plurality of sub-assets and the plurality ofsub-liabilities, the processing module 44 stores the sub-assets and theplurality of sub-liabilities as sub-asset information 690 andsub-liability information 726 in the database 30. A beneficial valuationelevation is created such that a sum of the benefit net present valueand the liability net present value is greater than the fair marketacquisition value so that the benefit entity and sponsor entity realizethe beneficial valuation elevation over direct utilization of selectedlongevity-contingent instruments of the updated set oflongevity-contingent instruments prior to the riving.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 17A-17C are schematic block diagrams of another embodiment of acommunication system illustrating an embodiment of a method forutilizing blockchain-encoded records for rived longevity-contingentinstruments within a computing system. The computing system includes abenefactor server 700, a debtor server 702, data sources 26-1 through26-N, a payer computing device 850, and the transactional server 18 ofFIG. 1 .

In an embodiment, the payer computing device 850 is implementedutilizing the augmentation server 24 FIG. 1 . In an embodiment, the datasources 26-1 through 26-N are implemented utilizing the data source 26of FIG. 1 . The transactional server 18 includes the processing module44 of FIG. 1 and the database 30 of FIG. 1 .

In an embodiment, the benefactor server 700 and the debtor server 702are implemented utilizing the legacy server 22 of FIG. 1 , where thebenefactor server 700 is associated with at least one benefit entity(e.g., pension system) and the debtor server 702 is associated with atleast one sponsor entity associated with the at least one benefitentity.

FIG. 17A illustrates an example of operation of steps of a method forthe utilizing blockchain-encoded records for rived longevity-contingentinstruments where, in a first step, the processing module 44 obtains afirst blockchain-encoded record 864 representing a firstlongevity-contingent instrument 722 of a set of longevity-contingentinstruments. When an insured person passes and a death benefit isprovided, availability of a benefit payout is utilized to fund acombination of a cash flow to a benefit entity and for at least some ofa plurality of premium payment streams on behalf of a sponsor entity,from the payer computing device 850 in accordance with a rive approach682. The first blockchain-encoded record 864 includes a notification ofthe death benefit.

The obtaining includes receiving one or more blockchain-encoded records860-1 through 860-N from one or more of the data sources 26-1 through26-N. The obtaining further includes receiving a blockchain-encodedrecord 862 from the payer computing device 850 when the payer computingdevice 850 issues the notification of the death benefit (e.g., the lifeinsurance company issues the notice).

Having obtained the first blockchain-encoded record 864, a second stepof the method for the utilizing blockchain-encoded records for rivedlongevity-contingent instruments includes the processing module 44verifying authenticity of the first blockchain-encoded record 864representing the first longevity-contingent instrument 722 of the set oflongevity-contingent instruments to produce a verified firstblockchain-encoded record. The set of longevity-contingent instrumentsis associated with a fair market acquisition value. The transactionalserver 18 maintains valuation information 880 within the database 30 toinclude the fair market acquisition value

The first longevity-contingent instrument 722 is selected and rived inaccordance with the rive approach 682 to reassign a first face valuebenefit of the first longevity-contingent instrument from a firstownership entity to the benefit entity to produce a first sub-asset of aplurality of sub-assets of the set of longevity-contingent instruments.The plurality of sub-assets is associated with a benefit net presentvalue. The transactional server 18 further maintains the valuationinformation 880 to include the benefit net present value. Thetransactional server 18 maintains sub-asset information 690 within thedatabase 30 to include information with regards to the plurality ofsub-assets.

The first longevity-contingent instrument 722 is further rived inaccordance with the rive approach 682 to reassign a first premiumpayment stream of the first longevity-contingent instrument from thefirst ownership entity to the sponsor entity to produce a firstsub-liability of a plurality of sub-liabilities of the set oflongevity-contingent instruments. The plurality of sub-liabilities isassociated with a liability net present value. The transactional server18 further maintains the valuation information 880 to include theliability net present value. The transactional server 18 maintainssub-liability information 726 within the database 30 to includeinformation with regards to the plurality of sub-liabilities The rivingcreates a beneficial valuation elevation such that a sum of the benefitnet present value and the liability net present value is greater thanthe fair market acquisition value so that the benefit entity and thesponsor entity realize the beneficial valuation elevation over directutilization of the set of longevity-contingent instruments prior to theriving.

The verifying of the authenticity of the first blockchain-encoded record864 includes utilizing a symmetric key signature approach or anotherapproach (e.g., straightforward signature verification). When utilizingthe symmetric key signature approach, the processing module 44 decryptsa first signature of the first blockchain-encoded record 864 utilizing afirst public key of a first public-private key pair to produce a firstdecrypted transaction hash value. The first public-private key pair isassociated with a last transaction computing device (e.g., a computingdevice associated with generating the death notification).

Having produced the first decrypted transaction hash value, theprocessing module 44 hashes a portion of the first blockchain-encodedrecord utilizing a second public key of a second public-private key pairto produce a candidate transaction hash value. The second public-privatekey pair is associated with the transactional server 18 (e.g., generatedby the transactional server 18). Having produced the candidatetransaction hash value, the processing module 44 indicates favorableauthenticity when the first decrypted transaction hash value comparesfavorably to the candidate transaction hash value.

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the first signature of thefirst blockchain-encoded record utilizing the first public key and thesecond public key to produce the favorable authenticity indication ofthe verified first blockchain-encoded record 864. The verifying of theauthenticity was previously discussed in greater detail with referenceto FIG. 14C.

Having verified the authenticity of the first blockchain-encoded record864, when the first longevity-contingent instrument 722 is associatedwith an available and unfulfilled benefit status, a third step of themethod for the utilizing blockchain-encoded records for rivedlongevity-contingent instruments includes the processing module 44determining fulfillment information 863 of the firstlongevity-contingent instrument. The determining of the fulfillmentinformation 863 includes determining that the first longevity-contingentinstrument 722 is associated with the available and unfulfilled benefitstatus. The processing module 44 determines that the firstlongevity-contingent instrument 722 is associated with an available andunfulfilled benefit status by at least one of several approaches.

A first approach includes interpreting the first longevity-contingentinstrument 722 to identify a first death-notification of a first insuredperson identifier. The first insured person identifier is associatedwith the first longevity-contingent instrument 722. A second approachincludes interpreting the first longevity-contingent instrument 722 toidentify the unfulfilled benefit status of the firstlongevity-contingent instrument 722. A third approach includes accessinglongevity-contingent instrument information from the database 30 toextract a set of insured person identifiers of the set oflongevity-contingent instruments and identifying the first insuredperson identifier within the plurality of insured person identifiers.

Having determined that the first longevity-contingent instrument 722 isassociated with the available and unfulfilled benefit status, theprocessing module 44 determines the fulfillment information 863 for thefirst longevity-contingent instrument 722. The fulfillment information863 includes a benefit payout of the first sub-asset facilitated by thepayer computing device 850 for the benefit entity.

The fulfillment information 863 includes a variety of one or moreelements. The elements include an identifier of the computing device, anidentifier of the benefactor server 700 associated with the benefitentity, an identifier of the debtor server 702 associated with thesponsor entity, and an identifier of the payer computing device 850. Theelements of the fulfillment information 863 further includes a requestfor the payment of the benefit payout, a current purchase transactionvalue, the benefit payout, and a fulfillment status of the benefitpayout.

The elements of the fulfillment information 863 further includes anownership entity identifier, a holder identifier, an insured personidentifier, an identifier of an associated blockchain-encoded record, anidentifier of an associated longevity-contingent instrument, a healthrecord, and an updated life expectancy value. The elements of thefulfillment information 863 further includes a death-notification of theinsured person identifier, an updated longevity status indicator, and anidentifier of another longevity-contingent instrument associated withthe first longevity-contingent instrument 722.

The determining of the fulfillment information 863 further includes atleast one of a variety of approaches. A first approach includesdetermining the benefit payout associated with the first sub-asset. Asecond approach includes generating a request for the payment of thebenefit payout. A third approach includes determining a first portion ofthe benefit payout to associate with a premium cash escrow in accordancewith the rive approach 682. The premium cash escrow is utilized to fundpayment of a plurality of premium payment streams associated with theplurality of sub-liabilities of the portfolio of longevity-contingentinstruments on behalf of the sponsor entity.

A third approach includes determining a second portion of the benefitpayout to associate with a benefit cash account based on the firstportion of the payout and in accordance with the rive approach 682. Thebenefit cash account is associated with the benefit entity (e.g., one ormore benefactors) associated with the benefactor server 700.

FIG. 17B further illustrates the example of operation of steps of themethod for the utilizing blockchain-encoded records for rivedlongevity-contingent instruments where, having determined thefulfillment information 863, in a fourth step the processing module 44verifies authenticity of an asset blockchain-encoded record 900representing the plurality of sub-assets to produce a verified assetblockchain-encoded record 904. The verifying of the authenticity of theasset blockchain-encoded record 900 includes obtaining the assetblockchain-encoded record 900 from at least one of the database 30 andthe benefactor server 700.

The verifying of the authenticity of the asset blockchain-encoded record900 further includes utilizing a symmetric key signature approach oranother approach (e.g., straightforward signature verification). Whenutilizing the symmetric key signature approach, the processing module 44decrypts a first signature of the asset blockchain-encoded record 900utilizing a first public key of a first public-private key pair toproduce a first decrypted transaction hash value. The firstpublic-private key pair is associated with a last transaction computingdevice (e.g., of the benefactor server 700, or of the transactionalserver 18, or of another computing device).

Having produced the first decrypted transaction hash value, theprocessing module 44 hashes a portion of the asset blockchain-encodedrecord 900 utilizing a second public key of a second public-private keypair to produce a candidate transaction hash value. The secondpublic-private key pair is associated with the transactional server 18(e.g., generated by the transactional server 18). Having produced thecandidate transaction hash value, the processing module 44 establishesthe verified asset blockchain-encoded record 904 to indicate favorableauthenticity when the first decrypted transaction hash value comparesfavorably to the candidate transaction hash value (e.g., substantiallythe same).

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the first signature of theasset blockchain-encoded record 900 utilizing the first public key andthe second public key to establish the verified asset blockchain-encodedrecord 904 to indicate the favorable authenticity. The verifying of theauthenticity of blocks of blockchains such as the assetblockchain-encoded record 900 was previously discussed in greater detailwith reference to FIG. 14C.

Having produced the verified asset blockchain-encoded record 904, afifth step of the example of operation of the method for the utilizingblockchain-encoded records for rived longevity-contingent instrumentsincludes the processing module 44 verifying authenticity of a liabilityblockchain-encoded record 902 representing the plurality ofsub-liabilities to produce a verified liability blockchain-encodedrecord 906. The verifying of the authenticity of the liabilityblockchain-encoded record 902 includes obtaining the liabilityblockchain-encoded record 902 from at least one of the database 30, thedebtor server 702, and any other computing device.

The verifying of the authenticity of the liability blockchain-encodedrecord 902 further includes utilizing the symmetric key signatureapproach or the other approach (e.g., straightforward signatureverification). When utilizing the symmetric key signature approach, theprocessing module 44 decrypts a first signature of the liabilityblockchain-encoded record 902 utilizing another first public key ofanother first public-private key pair to produce another first decryptedtransaction hash value. The other first public-private key pair isassociated with a last transaction computing device (e.g., of the debtorserver 702, or the transactional server 18, or another computingdevice).

Having produced the other first decrypted transaction hash value, theprocessing module 44 hashes a portion of the liabilityblockchain-encoded record 902 utilizing the second public key of thesecond public-private key pair to produce another candidate transactionhash value. The second public-private key pair is associated with thetransactional server 18 (e.g., generated by the transactional server18). Having produced the other candidate transaction hash value, theprocessing module 44 establishes the verified liabilityblockchain-encoded record 906 to indicate favorable authenticity whenthe other first decrypted transaction hash value compares favorably tothe other candidate transaction hash value (e.g., substantially thesame).

When not utilizing the symmetric key signature approach, the processingmodule 44 applies signature verification to the first signature of theliability blockchain-encoded record utilizing the other first public keyand the second public key to establish the verified liabilityblockchain-encoded record 906 to indicate the favorable authenticity.The verifying of the authenticity of blocks of blockchains such as theliability blockchain-encoded record 902 was previously discussed ingreater detail with reference to FIG. 14C.

FIG. 17C further illustrates the example of operation of steps of themethod for the utilizing blockchain-encoded records for rivedlongevity-contingent instruments where, having produced the verifiedasset blockchain-encoded record 904 and the verified liabilityblockchain-encoded record 906, in a sixth step the processing module 44facilitates exclusion of the first longevity-contingent instrument fromthe set of longevity-contingent instruments in accordance with thefulfillment information 863. The facilitating of the exclusion includesthe processing module 44 excluding the first sub-asset from theplurality of sub-assets to produce an updated plurality of sub-assets.The transactional server 18 maintains information with regards to theupdated plurality of sub-assets as updated sub-asset information 908.

The facilitating of the exclusion further includes the processing module44 excluding the first sub-liability from the plurality ofsub-liabilities to produce an updated plurality of sub-liabilities. Thetransactional server 18 maintains information with regards to theupdated plurality of sub-liabilities as updated sub-liabilityinformation 910.

The facilitating of the exclusion further includes the processing module44 updating the verified asset blockchain-encoded record 904 torepresent the updated plurality of sub-assets and updating the verifiedliability blockchain-encoded record 906 to represent the updatedplurality of sub-liabilities. The updating of the verified assetblockchain-encoded record 904 includes a series of sub-steps. A firstsub-step includes generating asset transaction content 912 to includeone or more of a variety of elements. The elements include informationregarding the fulfillment information 863, information regarding asecond sub-asset, information regarding the first sub-asset, informationregarding the updated plurality of sub-assets, an identifier of an ownercomputing device associated with an ownership entity, and an identifierof a benefactor computing device associated with the benefit entity. Theelements further include an identifier of a debtor computing deviceassociated with the sponsor entity, an identifier of an associatedblockchain-encoded record, an identifier of an associatedlongevity-contingent instrument, a current purchase transaction value,and an ownership entity identifier. The elements further include aholder identifier, an updated life expectancy value, an updatedlongevity status indicator, and an identifier of anotherlongevity-contingent instrument of the set of longevity-contingentinstruments.

A second sub-step of the series of sub-steps includes hashing the assettransaction content 912 utilizing a recipient public key of a recipientcomputing device (e.g., of the benefactor server 700 or of thetransactional server 18) to produce a next transaction hash value. Athird sub-step includes encrypting the next transaction hash valueutilizing a private key of the transactional server 18 to produce a nexttransaction signature. A fourth sub-step includes generating a nextblockchain-encoded record to include the asset transaction content 912and the next transaction signature.

The updating of the verified liability blockchain-encoded record 906includes another series of sub-steps. A first sub-step includesgenerating liability transaction content 914 to include one or more of avariety of elements. The elements include information regarding thefulfillment information 863, information regarding a secondsub-liability, information regarding the first sub-liability,information regarding the updated plurality of sub-liabilities, theidentifier of the owner computing device associated with the ownershipentity, and the identifier of the benefactor computing device associatedwith the benefit entity. The elements further include the identifier ofthe debtor computing device associated with the sponsor entity, theidentifier of the associated blockchain-encoded record, the identifierof the associated longevity-contingent instrument, the current purchasetransaction value, and the ownership entity identifier. The elementsfurther include the holder identifier, the updated life expectancyvalue, the updated longevity status indicator, and the identifier ofanother longevity-contingent instrument of the set oflongevity-contingent instruments.

A second sub-step of the other series of sub-steps includes hashing theliability transaction content 914 utilizing a recipient public key of arecipient computing device (e.g., of the debtor server 702 or of thetransactional server 18) to produce another next transaction hash value.A third sub-step includes encrypting the other next transaction hashvalue utilizing the private key of the transactional server 18 toproduce another next transaction signature. A fourth sub-step includesgenerating another next blockchain-encoded record to include theliability transaction content 914 and the other next transactionsignature.

Having updated the verified asset blockchain-encoded record 904 and theverified liability blockchain-encoded record 906, the processing module44 facilitates sharing of the updates. For example, the processingmodule 44 sends, via the network 28 of FIG. 1 , the verified assetblockchain-encoded record 904 to the benefactor server 700. As anotherexample, the processing module 44 sends, via the network 28 of FIG. 1 ,the verified liability blockchain-encoded record 906 to the debtorserver 702.

The method described above module can alternatively be performed byvarious modules of the communication system 10 of FIG. 1 or by otherdevices. In addition, at least one memory section (e.g., a computerreadable memory, a non-transitory computer readable storage medium, anon-transitory computer readable memory organized into a first memoryelement, a second memory element, a third memory element, a fourthelement section, a fifth memory element etc.) that stores operationalinstructions can, when executed by one or more processing modules of oneor more computing devices (e.g., one or more servers) of thecommunication system 10, cause the one or more computing devices toperform any or all of the steps described above.

FIGS. 18A-18E are schematic block diagrams of an embodiment of acomputing system illustrating an embodiment of a method for utilizing acontingent action token within the computing system. The computingsystem includes the benefactor server 700 of FIG. 13A, the debtor server702 of FIG. 13A, the user devices 32-1 through 32-N of FIG. 13A, thelongevity-contingent instrument provider servers 704-1 through 704-M ofFIG. 13A, the control server 20 of FIGS. 1 , and the transactionalserver 18 of FIG. 1 .

The control server 20 includes the processing module 44 of FIG. 1 andthe database 30 of FIG. 1 . The benefactor server 700 may be furtherassociated with an outcome recipient identifier 1128 as furtherdiscussed below. The debtor server 702 may be further associated with anobligation provider identifier 1146 as further discussed below. Thelongevity-contingent instrument provider servers 704-1 through 704-M mayfurther be associated with one or more of an outcome provider identifier1124 and an obligation recipient identifier 1150 as further discussedbelow. The transactional server 18 includes the processing module 44FIG. 1 and the database 30 of FIG. 1 and functions as a blockchain nodeof a blockchain associated with an object distributed ledger.

FIG. 18A illustrates an example of the method for utilizing thecontingent action token, where a first step of the example methodincludes the control server 20 identifying a non-fungible token (NFT) ofan object distributed ledger that meets minimum NFT requirements.Example content of the contingent action token 1000 is discussed ingreater detail with reference to FIG. 18B.

The minimum NFT requirements include a variety of requirements. A firstrequirement includes a recovered cryptographic token value 1112 of theNFT matches a calculated cryptographic token value of the NFT. A secondrequirement includes an obligation provider identifier 1146 of the NFTis the same as an original obligation provider identifier of the NFTwhen the NFT was initially generated. The obligation provider identifier1146 is associated with providing of an obligation 1148 tied to anobligation recipient identifier 1150 in accordance with obligationrequirements 1142. A positive obligation status 1144 indicates that theobligation 1148 has historically been provided in accordance with theobligation requirements 1142.

A second requirement includes an outcome recipient identifier 1128 ofthe NFT is the same as an original outcome recipient identifier of theNFT when the NFT was initially generated. The outcome recipientidentifier 1128 is associated with a result of a triggered outcome 1126tied to an outcome provider identifier 1124 in accordance withcontingent outcome rules 1118 and the positive obligation status 1144. Acontingency status 1120 indicates whether the triggered outcome 1126 hasbeen triggered for a contingency entity identifier 1122 in accordancewith the contingent outcome rules 1118.

The identifying the NFT of the object distributed ledger that meets theminimum NFT requirements includes a series of sub-steps. A firstsub-step includes the processing module 44 of the control server 20determining whether to indirectly or directly access the objectdistributed ledger. For example, the processing module 44 determines toindirectly access the object distributed ledger when the blockchain 1004is not available in the database 30 of the control server 20 and isavailable in the database 30 of the transactional server 18. As anotherexample, the processing module 44 of the control server 20 determines todirectly access the object distributed ledger when the blockchain 1004is available within the database 30 of the control server 20.

When indirectly accessing the object distributed ledger, a secondsub-step of the identifying of the NFT includes the processing module 44of the control server 20 issuing a non-fungible token access request tothe transactional server 18 (e.g., an object ledger computing device ofthe computing system serving as a blockchain node of the objectdistributed ledger). The non-fungible token access request includes arepresentation of the minimum NFT requirements. The second sub-stepfurther includes the processing module 44 of the control server 20extracting an NFT identifier of the NFT from a non-fungible token accessresponse that includes the contingency action token 1000 from thetransactional server 18, where the transactional server 18 accesses theobject distributed ledger 1002 to identify and NFT block 3 of theblockchain as illustrated in FIG. 18A.

When directly accessing the object distributed ledger, the secondsub-step of the identifying of the NFT includes the processing module 44of the control server 20 obtaining a copy of the object distributedledger (e.g., recover the blockchain 1004 from the database 30 of thecontrol server 20). The second sub-step further includes the processingmodule 44 of the control server 20 indicating the NFT identifier of theNFT when detecting a block of the copy of the object distributed ledgerthat matches the representation of the minimum NFT requirements (e.g.,original obligation provider identifier and original outcome recipientidentifier).

Having obtained the NFT, a third sub-step of the identifying of the NFTthat meets the minimum NFT requirements includes the processing module44 of the control server 20 verifying that the recovered cryptographictoken value 1112 of the NFT matches the calculated cryptographic tokenvalue of the NFT. For example, the processing module 44 produces thecalculated cryptographic token value of the NFT over a correspondingcontent portion of the obtained NFT and compares that calculated valueto the recovered cryptographic token value 1112. When the cryptographictoken values are the same, the processing module 44 indicates that theNFT that meets the minimum NFT requirements has been identified (e.g.,by the token identifier 1110).

FIG. 18B illustrates an example of elements of the contingency actiontoken 1000 of the example of the method for utilizing the contingentasset token. A token identifier 1110 uniquely identifies the contingencyaction token 1000. A cryptographic token value 1112 includes one or moreof public keys, a cryptographic signature over a portion of the token, anonce for utilization in a blockchain, and one or more hash values overportions of this token or another of a shared blockchain.

The token further includes blockchain linking information 1114 such astoken identifiers and/or links for other tokens of the sharedblockchain. A contingency type 1116 indicates a contingency category forthe token (e.g., where the contingency, when met, activates thetriggered outcome 1126). Contingent outcome rules 1118 set forth how theactivation of the triggered outcome is properly enabled. For example,activation only when the obligation status 1144 is positive and atrigger occurs associated with the contingency type.

A contingency status 1120 indicates whether the contingency has beentriggered (e.g., yes or no). A contingency entity identifier (ID) 1122specifies a unique identifier of an entity associated with thecontingency, where the contingent outcome rules dictate what happenswhen the contingency trigger occurs associated with the contingencyentity identifier.

An outcome provider ID 1124 indicates an identifier associated withproviding of the triggered outcome when activated. The triggered outcome1126 occurs when activated and in accordance with the contingent outcomerules. An outcome recipient ID 1128 is associated with receiving of thetriggered outcome 1126.

Obligation requirements 1142 indicate an obligation and timing by anobligation provider identifier to an obligation recipient identifier.The obligation status 1144 indicates historically whether the obligationhas been maintained as associated with the obligation provider ID 1146.The obligation 1148 indicates metrics and/or descriptors associated withan obligation provided in association with the obligation provider ID toan association of the obligation recipient ID 1150.

The contingent action token 1000 further includes elements associatedwith evaluating portions of the token in accordance with an evaluationprofile 1138 (e.g., risk assumptions, historical probabilities and risksof obligations and outcomes). Major portions of the token include theobligation and the triggered outcome. An obligation evaluation 1156evaluates the obligation by utilizing an obligation disruption riskassessment 1152 that portrays likelihood of disruption of an obligationstream when the obligation includes a series of sub componentobligations. The obligation evaluation is further based on a probabilityof obligation met 1154 wrapping up a risk assessment of an associationof the obligation provider ID faithfully providing the obligation to theassociation of the obligation recipient ID.

An outcome evaluation 1140 provides an evaluation of the triggeredoutcome based on an estimated obligation status at estimated outcometriggered date 1130 that portrays risk of a negative obligation statusat an expected time of the trigger of the triggered outcome. The outcomeevaluation is further based on estimating that outcome triggered date1134 in accordance with parameters of estimated outcome triggered date1132 (e.g., historical values of trigger date timing and variablescorrelated to the contingency entity identifier). The outcome evaluationis further based on an outcome provider probability to perform outcome1136 that assesses whether an association of the outcome provider ID isable to provide the triggered outcome at the estimated outcome triggerdate.

The evaluation of the token further includes a rollup of the obligationevaluation and the outcome evaluation in a combined evaluation ofcombination of outcome and obligation 1158. The combined evaluationprovides an all-in preponderance of a present evaluation based on anestimated future that concludes with the trigger outcome. Risksassociated with both the obligation and the triggered outcome drive thecombined evaluation such that changing of the obligation provider ID canresult in an unexpected improvement in the combined evaluation. Forexample, the outcome evaluation 1140 can rise to an improved evaluationwhen the obligation provider ID is changed to another obligationprovider ID that is associated with a higher probability of obligationmet 1154. With that, the estimated obligation status at estimatedoutcome triggered date 1130 improves driving up the outcome evaluation1140.

A series of related invention embodiments pertain to finding change outsof one or more of the obligation provider ID and the outcome recipientID to provide an improved combined evaluation. As a result, a beneficialevaluation increase is provided. As a specific example, the token isoriginally set up with an original obligation provider ID that is thesame as the contingency entity ID, an original outcome recipient ID, andan outcome provider ID that matches the obligation recipient ID. Later,the token is updated to replace the obligation provider ID with anotherobligation provider ID associated with a higher probability of providingthe obligation (e.g., that may or may not include the contingency entityID). As a result, the outcome evaluation 1140 rises to an improved andunexpected level of the invention embodiment.

FIG. 18C further illustrates the example of the method for utilizing thecontingent asset token, where having identify the NFT that meets theminimum NFT requirements, a second step of the example method includesthe control server 20 determining whether to select the NFT based on anevaluation of the NFT with regards to an evaluation profile 1138. Abeneficial improvement to the triggered outcome results from ahypothetical change to the obligation provider identifier of theselected NFT. The evaluation of the NFT includes producing theobligation evaluation 1156 based on the evaluation profile 1138. Theobligation evaluation 1156 compares the providing of the obligation inaccordance with the obligation requirements (e.g., historical andestimated future). The evaluation of the NFT further includes theoutcome evaluation 1140. The outcome evaluation 1140 estimates thetriggered outcome based on the evaluation profile 1138 (e.g., usingrisks and historical correlations of the evaluation profile).

The determining whether to select the NFT based on the evaluation of theNFT with regards to the evaluation profile includes a series ofsub-steps. A first sub-step includes the processing module 44 of thecontrol server 20 determining the evaluation profile to include arequired evaluation performance improvement level. For example, theprocessing module 44 extracts the evaluation profile 1138 from therecovered NFT. As another example, the processing module 44 generatesthe evaluation profile based on an external input through a userinterface (e.g., a request that includes s specific evaluationperformance improvement level.

A second sub-step includes the processing module 44 of the controlserver 20 comparing the providing of the obligation associated with theoriginal obligation provider identifier to providing of the obligationassociated with a hypothetical obligation provider identifier inaccordance with the evaluation profile to produce the obligationevaluation. For example, the processing module 44 receives identity andrisk levels with regards to a new obligation provider identifier andutilizes that to produce the obligation evaluation (e.g., an improvedoutcome when a risk level of noncompliance to the obligation is lowerfor the new obligation provider identifier).

A third sub-step includes the processing module 44 of the control server20 comparing an estimated trigger outcome when the providing of theobligation is associated with the original obligation provideridentifier to a hypothetical estimated trigger outcome when theproviding of the obligation is associated with the hypotheticalobligation provider identifier in accordance with the evaluation profileto produce the outcome evaluation. For example, the processing module 44produces the outcome evaluation for the new obligation provider (e.g.,with the lower risks of not meeting the obligation) and for an estimatedtrigger date of the triggered outcome.

A fourth sub-step includes the processing module 44 of the controlserver 20 indicating to select the NFT when the obligation evaluationand the outcome evaluation satisfies the required evaluation performanceimprovement level. For example, the processing module 44 indicates toselect the NFT when the new obligation provider identifier is a catalystto meet the required evaluation performance improvement level.

FIG. 18D further illustrates the example of the method for utilizing thecontingent asset token, where having selected the NFT to produce aselected NFT, a third step of the example method includes determiningreassignment information for the selected NFT. The reassignmentinformation includes a confirmed change of at least one of theobligation provider identifier 1146 and the outcome recipient identifier1128.

The determining the reassignment information for the selected NFTincludes a variety of approaches. A first approach includes identifyinga hypothetical obligation provider identifier based on the evaluation ofthe selected NFT with regards to the evaluation profile to establish anew obligation provider identifier of the reassignment information. Forexample, the processing module 44 of the control server 20 replaces oradds a hypothetical obligation provider identifier to the obligationprovider identifier 1146 based on a previous analysis of the evaluationof the selected NFT. Acquisition of the hypothetical obligation provideridentifier includes extracting the identifier from confirmationinformation 1170 received from another computing device and extractionfrom content 1006 of the selected NFT.

A second approach to determine the reassignment information includes,when requested, the processing module 44 of the control server 20modifying the outcome recipient identifier to establish a new outcomerecipient identifier of the reassignment information. For example, theprocessing module 44 extracts the new outcome recipient identifier fromthe confirmation information 1170.

Having determined the reassignment information, a fourth step of theexample method of operation includes the processing module 44 of thecontrol server 20 facilitating taking control of the selected NFT of ablockchain of the object distributed ledger as discussed with referenceto FIG. 14C. For example, the processing module 44 exchanges controlgrant information 1172 with a current controlling entity of the selectedNFT to gain the control. For instance, the current controlling entitygenerates a new block that includes a public key of the processingmodule 44, the control request from the processing module 44, and acryptographic signature over a portion of the block utilizing a privatekey of the current controlling entity.

FIG. 18E further illustrates the example of the method for utilizing thecontingent asset token, where having taking control of the selected NFT,a fifth step of the example method includes the processing module 44 ofthe control server 20 updating the selected NFT utilizing thereassignment information for the NFT to produce an updated NFT 1180. Theupdating the selected NFT utilizing the reassignment information for theselected NFT to produce the updated NFT 1180 includes a series ofsub-steps. A first sub-step includes the processing module 44 obtainingthe selected NFT. For example, the processing module 44 recovers theselected NFT from the blockchain 1004 of the database 30 of the controlserver 20 when a local copy of the blockchain is up-to-date. As anotherexample, the processing module 44 requests the selected NFT from thetransactional server 18.

A second sub-step includes the processing module 44 replacingcorresponding elements of the selected NFT with at least a portion ofthe reassignment information to produce the updated NFT 1180. Forexample, the processing module 44 replaces the obligation provideridentifier 1146 with a new obligation provider identifier such that thebeneficial valuation level increase is realized subsequently for thetriggered outcome upon triggering and when conditions of the contingentoutcome rules have been satisfied.

Having produced the updated NFT 1180, a sixth step of the example methodof operation includes the processing module 44 of the control server 20causing generation of a new block affiliated with the updated NFT viathe blockchain of the object distributed ledger. The new block includesthe updated NFT.

The causing generation of the new block affiliated with the updated NFTvia the blockchain of the object distributed ledger includes a series ofsub-steps. A first sub-step includes the processing module 44 of thecontrol server 20 determining whether to indirectly or directly updatethe object distributed ledger as previously discussed (e.g., using alocal copy of the blockchain when available).

When indirectly updating the object distributed ledger, a secondsub-step includes the processing module 44 issuing a blockchain updaterequest to an object ledger computing device of the computing systemserving as a blockchain node of the object distributed ledger. Theblockchain update request includes the updated NFT 1180. For example,the processing module 44 of the control server sends the updated NFT1180 to the transactional server 18 such that the transactional server18 places an update 1 block 3-1 on the blockchain connected to the NFTas illustrated in FIG. 18E.

When directly updating the object distributed ledger, the secondsub-step includes the processing module 44 obtaining a copy of theobject distributed ledger. For example, the processing module 44recovers the object distributed ledger from the blockchain 1004 of thedatabase 30 of the control server 20. Having obtained the copy of theobject distributed ledger, the second sub-step further includes hashingcontent of the updated NFT utilizing a receiving public key of theobject distributed ledger to produce a next transaction hash value. Forexample, the control module 44 generates a hash value utilizing acryptographic algorithm over the content of the updated NFT using apublic key in possession of receiving entities for subsequent access ofthe blockchain to produce the next transaction hash value.

Having produced the next transaction hash value, the second sub-stepfurther includes encrypting the next transaction hash value utilizing aprivate key of the computing device to produce a next transactionsignature. For example, the processing module 44 utilizes acryptographic encryption algorithm to encrypt the next transaction hashvalue utilizing the private key of the processing module 44 to producethe next transaction signature.

Having produced the next transaction signature, the second sub-stepfurther includes generating a next block of the blockchain of the objectdistributed ledger to include the content of the updated NFT and thenext transaction signature. For example, the processing module 44populates the cryptographic token value 1112 of the next block with thenext transaction signature and populates all the other content fieldswith the content of the updated NFT to produce the next block.

Having produced the next block, the second sub-step further includescausing inclusion of the next block as the new block in the objectdistributed ledger. For example, the processing module 44 of the controlserver 20 adds the block 3-1 as the update 1 associated with theselected NFT on the object distributed ledger 1002 as illustrated inFIG. 18E by updating the blockchain 1004 and the database of the controlserver 20 and/or the transactional server 18 and other transactionalservers serving as blockchain nodes supporting the object distributedledger.

Alternatively, or in addition to, the processing module 44 of thecontrol server 20 sends the updated NFT 1182 one or more of thebenefactor server 700, the debtor server 702, one or more of the userdevices 32-1 through 32-N, and one or more of the longevity-contingentinstrument provider servers 704-1 through 704-M.

The method described above module can alternatively be performed byvarious modules of the computing system or by other devices. Inaddition, at least one memory section (e.g., a computer readable memory,a non-transitory computer readable storage medium, a non-transitorycomputer readable memory organized into a first memory element, a secondmemory element, a third memory element, a fourth element section, afifth memory element etc.) that stores operational instructions can,when executed by one or more processing modules of one or more computingdevices (e.g., one or more servers) of the computing system, cause theone or more computing devices to perform any or all of the stepsdescribed above.

FIGS. 19A-19B are schematic block diagrams of another embodiment of acomputing system illustrating another embodiment of a method forgenerating a contingent action token within the computing system. Thecomputing system includes the benefactor server 700 of FIG. 13A, thedebtor server 702 of FIG. 13A, the user devices 32-1 through 32-N ofFIG. 13A, accreditation authority servers 1200-1 through 1200-M, thecontrol server 20 of FIG. 1 , and the transactional server 18 of FIG. 1. In an embodiment, the accreditation authority server is affiliatedwith a corresponding longevity-contingent instrument provider server 704of FIG. 13A. The control server 20 includes the processing module 44 ofFIG. 1 and the database 30 of FIG. 1 . The transactional server 18includes the processing module 44 FIG. 1 and the database 30 of FIG. 1and functions as a blockchain node of a blockchain 1004 associated withan object distributed ledger 1002.

FIG. 19A illustrates an example method of operation for generating thecontingent action token, where a first step of the example methodincludes the control server 20 interpreting a request to generate anon-fungible token (NFT) 1202 as a contingency action token for theobject distributed ledger 1002 to produce baseline content of content1006 that includes an obligation provider identifier (ID) 1146 and anoutcome recipient ID 1128. The obligation provider ID is associated withproviding of an obligation tied to an obligation recipient ID 1150 inaccordance with obligation requirements 1142. The outcome recipient ID1128 is associated with a result of a triggered outcome 1126 tied to anoutcome provider ID 1124 in accordance with contingent outcome rules andan obligation status. A positive obligation status indicates that theobligation has historically been provided in accordance with theobligation requirements 1142. The format of the contingent action token1000 is discussed in greater detail with reference to FIG. 18B.

The baseline content for the contingency action token further includes acontingency entity identifier (ID) 1122, an outcome provider ID 1124, avalue of a triggered outcome 1126, the outcome recipient ID 1128, theobligation requirements 1142, the obligation provider ID 1146, and theobligation recipient ID 1150. The interpreting the request to generatethe NFT to produce the baseline content includes a series of sub-steps.A first sub-step includes the processing module 44 of the control server20 extracting, from the request to generate the NFT 1202, one or more ofthe contingency entity ID 1122, the outcome provider ID 1124, the valueof the result of the triggered outcome 1126, the obligation requirements1142, and the obligation recipient ID 1150.

A second sub-step includes the processing module 44 determining theoutcome recipient ID 1128 based on the request to generate the NFT 1202and benefactor information (e.g., which entity or entities is to receivethe result of the triggered outcome 1126). For example, the processingmodule 44 interprets the benefactor information to identify an entitythat is to receive the result of the triggered outcome and to establishan identifier of the entity as the outcome recipient ID 1128.

A third sub-step includes the processing module 44 determining theobligation provider ID 1146 based on the request to generate the NFT anddebtor information (e.g., which entity or entities are to provide, atleast in part, the obligation in accordance with the obligationrequirements 1142). For example, the processing module 44 interprets thedebtor information to identify an entity that is to provide theobligation and to establish an identifier of the entity as theobligation provider 1146.

Having produced the baseline content, a second step of the examplemethod of operation includes the processing module 44 verifying with anaccreditation authority computing device of the computing system,validity of the baseline content. In an embodiment, one or more of theaccreditation authority servers 1200-1 through 1200-M provide theaccreditation authority computing device.

The verifying the validity of the baseline content includes a series ofsub-steps. A first sub-step includes the processing module 44 of thecontrol server 20 identifying the accreditation authority computingdevice based on a first identified corresponding accreditation authorityassociated with the obligation recipient ID 1150. For example, thecontrol server 20 accesses the database 30 to retrieve identity of theaccreditation authority server 1200-1 that is affiliated with theobligation provider ID.

A second sub-step includes the processing module 44 obtaining baselinevalidation information 1204 from the accreditation authority computingdevice for the baseline content. For example, the processing module 44issues at least some of the baseline content to the accreditationauthority server 1200-1 and receives the baseline validation information1204 in response.

A third sub-step includes the processing module 44 indicating that thebaseline content is valid when the baseline validation information issubstantially the same as the baseline content. For example, theprocessing module 44 compares the received baseline validationinformation 1204 2 the baseline content and indicates that the baselinecontent is valid when the comparison indicates a match of at least aminimum set of items for matching (e.g., outcome provider ID 1124, andobligation recipient ID 1150).

FIG. 19B further illustrates the example method of operation of thegenerating of the contingent action token, where having verified thebaseline content as valid, a third step includes the processing module44 of the control server 20 determining whether a beneficial improvementis provided to the result of the triggered outcome 1126 when ahypothetical change to the obligation provider ID 1146 is made. Thehypothetical change includes utilizing a different obligation providerID with a different risk profile as compared to a baseline risk profileassociated with a present obligation provider ID.

The determining whether the beneficial improvement is provided includesproducing an obligation evaluation based on an evaluation profile. Theobligation evaluation compares the providing of the obligation inaccordance with the obligation requirements with the hypothetical changeto the obligation provider ID. The determining further includesproducing an outcome evaluation. The outcome evaluation estimates theresult of the triggered outcome based on the evaluation profile when thehypothetical change to the obligation provider ID is made. For example,an improvement to the result of the triggered outcome may occur when alower risk profile of the hypothetical change to the obligation providerID is implemented.

The determining whether the beneficial improvement is provided to theresult of the triggered outcome when the hypothetical change to theobligation provider ID is made includes a series of sub-steps. A firstsub-step includes the processing module 44 of the control server 20generating an obligation disruption risk assessment 1152 for the(present) obligation provider ID 1146 based on the evaluation profile toproduce a baseline obligation evaluation. For example, the processingmodule 44 analyzes risks associated with obligation fulfillmentassociated with the present obligation provider ID.

A second sub-step includes the processing module 44 generating anotherobligation disruption risk assessment for the hypothetical change to theobligation provider ID based on the evaluation profile to produce ahypothetical baseline obligation evaluation. For example, the processingmodule 44 analyzes risks associated with the obligation fulfillmentassociated with the hypothetical change to the obligation provider ID.

A third sub-step includes the processing module 44 generating a baselineoutcome evaluation to include an estimate of the result of the triggeredoutcome utilizing the baseline obligation evaluation. For example, theprocessing module 44 computes the result of the triggered outcome whenobligation risks associated with the present obligation provider ID areconsidered.

A fourth sub-step includes the processing module 44 generating theoutcome evaluation to include another estimate of the result of thetriggered outcome utilizing the hypothetical baseline obligationevaluation. For example, the processing module 44 computes anotherresult of the triggered outcome when obligation risks associated withthe hypothetical change to the obligation provider ID our considered.

A fifth sub-step includes the processing module 44 indicating that thebeneficial improvement is provided to the result of the triggeredoutcome when the hypothetical change to the obligation provider ID ismade when the outcome evaluation is greater than the baseline outcomeevaluation. For example, the processing module 44 compares the resultsof the triggered outcome and indicates the beneficial improvement isprovided when the triggered outcome is greater utilizing thehypothetical change to the obligation provider ID (e.g., due to loweredrisks).

Having determined the beneficial improvement when the baseline contentas valid, a fourth step of the example method of operation includes theprocessing module 44 of the control server 20 establishing NFT contentbased on the outcome evaluation to include the baseline content. Theestablishing the NFT content based on the outcome evaluation to includethe baseline content includes a series of sub-steps. A first sub-stepincludes the processing module 44 generating the NFT content to includethe baseline content. For example, the processing module 44 includes thecontingency entity ID 1122, the outcome provider ID 1124, the triggeredoutcome 1126, the outcome recipient ID 1128, the obligation requirements1142, the obligation provider ID 1146, and the obligation recipient ID1150 in the NFT content.

A second sub-step includes the processing module 44 updating the NFTcontent to replace the obligation provider ID 1146 with an updatedobligation provider ID associated with the hypothetical change to theobligation provider ID when the beneficial improvement is provided tothe result of the triggered outcome from the hypothetical change to theobligation provider ID.

Having established the NFT content, a fifth step of the example methodof operation includes the processing module 44 of the control server 20causing generation of a new block affiliated with the NFT via theblockchain 1004 of the object distributed ledger 1002 as discussed withreference to FIG. 14C. The new block includes the NFT content. Thecausing generation of the new block includes a series of sub-steps. Afirst sub-step includes the processing module 44 determining whether toindirectly or directly update the object distributed ledger aspreviously discussed (e.g., using a local copy of the blockchain whenavailable).

When indirectly updating the object distributed ledger, a secondsub-step includes the processing module 44 of the control server 20issuing a blockchain update request to an object ledger computing deviceof the computing system serving as a blockchain node of the objectdistributed ledger. The blockchain update request includes the NFT 1210.For example, the processing module 44 sends the updated NFT 1210 to thetransactional server 18 such that the transactional server 18 places aNFT3 block 3 on the blockchain connected to the NFT 2 as illustrated inFIG. 19B.

When directly updating the object distributed ledger, the secondsub-step includes the processing module 44 obtaining a copy of theobject distributed ledger. For example, the processing module 44recovers the object distributed ledger from the blockchain 1004 of thedatabase 30 of the control server 20. Having obtained the copy of theobject distributed ledger, the second sub-step further includes hashingNFT content of the NFT utilizing a receiving public key of the objectdistributed ledger to produce a next transaction hash value. Forexample, the control module 44 generates a hash value utilizing acryptographic algorithm over the NFT content of the NFT using a publickey in possession of receiving entities for subsequent access of theblockchain to produce the next transaction hash value.

Having produced the next transaction hash value, the second sub-stepfurther includes encrypting the next transaction hash value utilizing aprivate key of the computing device to produce a next transactionsignature. For example, the processing module 44 utilizes acryptographic encryption algorithm to encrypt the next transaction hashvalue utilizing the private key of the processing module 44 to producethe next transaction signature.

Having produced the next transaction signature, the second sub-stepfurther includes generating a next block of the blockchain of the objectdistributed ledger to include the NFT content of the NFT and the nexttransaction signature. For example, the processing module 44 populatesthe cryptographic token value of the next block with the nexttransaction signature and populates all the other content fields withthe content of the NFT to produce the next block.

Having produced the next block, the second sub-step further includescausing inclusion of the next block as the new block in the objectdistributed ledger. For example, the processing module 44 of the controlserver 20 adds the block 3 on the object distributed ledger 1002 asillustrated in FIG. 19B by updating the blockchain 1004 and the database30 of the control server 20 and/or the transactional server 18 and othertransactional servers serving as blockchain nodes supporting the objectdistributed ledger.

Alternatively, or in addition to, the processing module 44 of thecontrol server 20 sends the NFT 1210 to one or more of the benefactorserver 700, the debtor server 702, one or more of the user devices 32-1through 32-N, and one or more of the accreditation authority servers1200-1 through 1200-M.

The method described above module can alternatively be performed byvarious modules of the computing system or by other devices. Inaddition, at least one memory section (e.g., a computer readable memory,a non-transitory computer readable storage medium, a non-transitorycomputer readable memory organized into a first memory element, a secondmemory element, a third memory element, a fourth element section, afifth memory element etc.) that stores operational instructions can,when executed by one or more processing modules of one or more computingdevices (e.g., one or more servers) of the computing system, cause theone or more computing devices to perform any or all of the stepsdescribed above.

FIGS. 20A-20B are schematic block diagrams of another embodiment of acomputing system illustrating another embodiment of a method forutilizing a contingent action token within the computing system. Thecomputing system includes the benefactor server 700 of FIG. 13A, thedebtor server 702 of FIG. 13A, the user devices 32-1 through 32-N ofFIG. 13A, accreditation authority servers 1200-1 through 1200-M, thecontrol server 20 of FIG. 1 , and the transactional server 18 of FIG. 1. In an embodiment, the accreditation authority server is affiliatedwith a corresponding longevity-contingent instrument provider server 704of FIG. 13A. The control server 20 includes the processing module 44 ofFIG. 1 and the database 30 of FIG. 1 . The transactional server 18includes the processing module 44 FIG. 1 and the database 30 of FIG. 1and functions as a blockchain node of a blockchain 1004 associated withan object distributed ledger 1002.

FIG. 20A illustrates an example of the method for utilizing thecontingent action token, where a first step of the example methodincludes the control server 20 detecting a change of contingency statusassociated with a contingency action token. For example, the processingmodule 44 of the control server 20 interprets a contingency status 1120from one or more of the benefactor server 700, the debtor server 702,one or more of the user devices 32-1 through 32-N, and one or more ofthe accreditation authority servers 1200-1 through 1200-M to identifythe change of the contingency status from not triggered to triggered fora particular contingency entity identifier 1122. In an embodiment, theprocessing module 44 further interprets the contingency status 1120 toextract the contingency action token 1000.

Having detected the change of contingency status, a second step of theexample method of operation includes recovering a non-fungible token(NFT) of an object distributed ledger that matches the contingencyaction token to produce a recovered NFT. For example, when indirectlyaccessing the NFT, the control server 20 receives the NFT 1210 from thetransactional server 18 with regards to the object distributed ledger1002 that includes the object NFT 3 of the NFT block 3 as illustrated inFIG. 20A based on a request associated with the contingency entityidentifier 1122 and/or a token identifier 1110 of the contingency actiontoken 1000. As another example, when directly accessing the NFT, theprocessing module 44 of the control server 20 recovers the NFT from alocal copy of the blockchain 1004 stored in the database 30 of thecontrol server 20.

Having recovered the NFT, a third step of the example method ofoperation includes determining, by the computing device, whether atriggered outcome 1126 is valid for the change of contingency statusbased on contingent outcome rules 1118 of the recovered NFT and anobligation status 1144 of an obligation tied to an obligation recipientidentifier 1150 in accordance with obligation requirements. A positiveobligation status indicates that the obligation has historically beenprovided in accordance with the obligation requirements. An outcomerecipient identifier 1128 is associated with a result of the triggeredoutcome 1126 tied to an outcome provider identifier 1124 in accordancewith the contingent outcome rules 1118 and the positive obligationstatus. The contingency status 1120 indicates whether the triggeredoutcome 1126 has been triggered for a contingency entity identifier 1122in accordance with the contingent outcome rules 1118. For example, theprocessing module 44 of the control server 20 approves the triggeroutcome as valid when the contingency status has triggered and theobligation status is positive in accordance with the contingent outcomerules 1118.

FIG. 20B further illustrates the example method of operation, wherehaving determined that the trigger outcome is valid, a fourth stepincludes determining NFT update information for the recovered NFT. TheNFT update information includes a confirmed change of at least one ofthe change of contingency status associated with the contingency entityand the trigger outcome is valid. For example, the processing module 44of the control server 20 updates the contingency status 1120 totriggered and updates the trigger outcome 1126 as valid within content1006 of the database 34 the contingency action token.

Having produced the NFT update information, a fifth step of the examplemethod of operation includes facilitating taking control of the NFT of ablockchain 1004 of the object distributed ledger 1002 as previouslydiscussed. For example, the control server 20 receives control grantinformation 1172 from a granting entity (e.g., a user device, andaccreditation authority server, a blockchain node).

Having taken control of the NFT, a sixth step of the example method ofoperation includes updating the recovered NFT utilizing the NFT updateinformation to produce an updated NFT. For example, the processingmodule 44 of the control server 20 updates the content 1006 of the NFTutilizing the NFT update information to produce the updated NFT.

Having produced the updated NFT, a seventh step of the example method ofoperation includes causing generation of a new block affiliated with theupdated NFT via the blockchain of the object distributed ledger aspreviously discussed. The new block includes the updated NFT. Forexample, when indirectly performing the placement, the processing module44 of the control server 20 sends the NFT 1210 (e.g., the updated NFT)to the transactional server 18 for storage in the blockchain 1004amongst blockchain nodes to produce the updated 1 of block 3-1 asillustrated in FIG. 20B. As another example, when directly performingthe placement, the processing module 44 of the control server 20 addsthe update 1 block to the blockchain of the object distributed ledger1002 as illustrated in FIG. 20B.

The method described above module can alternatively be performed byvarious modules of the computing system or by other devices. Inaddition, at least one memory section (e.g., a computer readable memory,a non-transitory computer readable storage medium, a non-transitorycomputer readable memory organized into a first memory element, a secondmemory element, a third memory element, a fourth element section, afifth memory element etc.) that stores operational instructions can,when executed by one or more processing modules of one or more computingdevices (e.g., one or more servers) of the computing system, cause theone or more computing devices to perform any or all of the stepsdescribed above.

It is noted that terminologies as may be used herein such as bit stream,stream, signal sequence, etc. (or their equivalents) have been usedinterchangeably to describe digital information whose contentcorresponds to any of a number of desired types (e.g., data, video,speech, text, graphics, audio, etc. any of which may generally bereferred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. For some industries, anindustry-accepted tolerance is less than one percent and, for otherindustries, the industry-accepted tolerance is 10 percent or more. Otherexamples of industry-accepted tolerance range from less than one percentto fifty percent. Industry-accepted tolerances correspond to, but arenot limited to, component values, integrated circuit process variations,temperature variations, rise and fall times, thermal noise, dimensions,signaling errors, dropped packets, temperatures, pressures, materialcompositions, and/or performance metrics. Within an industry, tolerancevariances of accepted tolerances may be more or less than a percentagelevel (e.g., dimension tolerance of less than +/−1%). Some relativitybetween items may range from a difference of less than a percentagelevel to a few percent. Other relativity between items may range from adifference of a few percent to magnitude of differences.

As may also be used herein, the term(s) “configured to”, “operablycoupled to”, “coupled to”, and/or “coupling” includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for an example of indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.

As may even further be used herein, the term “configured to”, “operableto”, “coupled to”, or “operably coupled to” indicates that an itemincludes one or more of power connections, input(s), output(s), etc., toperform, when activated, one or more its corresponding functions and mayfurther include inferred coupling to one or more other items. As maystill further be used herein, the term “associated with”, includesdirect and/or indirect coupling of separate items and/or one item beingembedded within another item.

As may be used herein, the term “compares favorably”, indicates that acomparison between two or more items, signals, etc., provides a desiredrelationship. For example, when the desired relationship is that signal1 has a greater magnitude than signal 2, a favorable comparison may beachieved when the magnitude of signal 1 is greater than that of signal 2or when the magnitude of signal 2 is less than that of signal 1. As maybe used herein, the term “compares unfavorably”, indicates that acomparison between two or more items, signals, etc., fails to providethe desired relationship.

As may be used herein, one or more claims may include, in a specificform of this generic form, the phrase “at least one of a, b, and c” orof this generic form “at least one of a, b, or c”, with more or lesselements than “a”, “b”, and “c”. In either phrasing, the phrases are tobe interpreted identically. In particular, “at least one of a, b, and c”is equivalent to “at least one of a, b, or c” and shall mean a, b,and/or c. As an example, it means: “a” only, “b” only, “c” only, “a” and“b”, “a” and “c”, “b” and “c”, and/or “a”, “b”, and “c”.

As may also be used herein, the terms “processing module”, “processingcircuit”, “processor”, “processing circuitry”, and/or “processing unit”may be a single processing device or a plurality of processing devices.Such a processing device may be a microprocessor, micro-controller,digital signal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, processing circuitry, and/or processing unitmay be, or further include, memory and/or an integrated memory element,which may be a single memory device, a plurality of memory devices,and/or embedded circuitry of another processing module, module,processing circuit, processing circuitry, and/or processing unit. Such amemory device may be a read-only memory, random access memory, volatilememory, non-volatile memory, static memory, dynamic memory, flashmemory, cache memory, and/or any device that stores digital information.Note that if the processing module, module, processing circuit,processing circuitry, and/or processing unit includes more than oneprocessing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,processing circuitry and/or processing unit implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element may store, and the processing module, module,processing circuit, processing circuitry and/or processing unitexecutes, hard coded and/or operational instructions corresponding to atleast some of the steps and/or functions illustrated in one or more ofthe Figures. Such a memory device or memory element can be included inan article of manufacture.

One or more embodiments have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims. One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with one or more other routines. In addition, a flow diagrammay include an “end” and/or “continue” indication. The “end” and/or“continue” indications reflect that the steps presented can end asdescribed and shown or optionally be incorporated in or otherwise usedin conjunction with one or more other routines. In this context, “start”indicates the beginning of the first step presented and may be precededby other activities not specifically shown. Further, the “continue”indication reflects that the steps presented may be performed multipletimes and/or may be succeeded by other activities not specificallyshown. Further, while a flow diagram indicates a particular ordering ofsteps, other orderings are likewise possible provided that theprinciples of causality are maintained.

The one or more embodiments are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical embodiment of an apparatus, an article ofmanufacture, a machine, and/or of a process may include one or more ofthe aspects, features, concepts, examples, etc. described with referenceto one or more of the embodiments discussed herein. Further, from figureto figure, the embodiments may incorporate the same or similarly namedfunctions, steps, modules, etc. that may use the same or differentreference numbers and, as such, the functions, steps, modules, etc. maybe the same or similar functions, steps, modules, etc. or differentones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theembodiments. A module implements one or more functions via a device suchas a processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes oneor more memory elements. A memory element may be a separate memorydevice, multiple memory devices, or a set of memory locations within amemory device. Such a memory device may be a read-only memory, randomaccess memory, volatile memory, non-volatile memory, static memory,dynamic memory, flash memory, cache memory, a quantum register or otherquantum memory and/or any other device that stores data in anon-transitory manner. Furthermore, the memory device may be in a formof a solid-state memory, a hard drive memory or other disk storage,cloud memory, thumb drive, server memory, computing device memory,and/or other non-transitory medium for storing data. The storage of dataincludes temporary storage (i.e., data is lost when power is removedfrom the memory element) and/or persistent storage (i.e., data isretained when power is removed from the memory element). As used herein,a transitory medium shall mean one or more of: (a) a wired or wirelessmedium for the transportation of data as a signal from one computingdevice to another computing device for temporary storage or persistentstorage; (b) a wired or wireless medium for the transportation of dataas a signal within a computing device from one element of the computingdevice to another element of the computing device for temporary storageor persistent storage; (c) a wired or wireless medium for thetransportation of data as a signal from one computing device to anothercomputing device for processing the data by the other computing device;and (d) a wired or wireless medium for the transportation of data as asignal within a computing device from one element of the computingdevice to another element of the computing device for processing thedata by the other element of the computing device. As may be usedherein, a non-transitory computer readable memory is substantiallyequivalent to a computer readable memory. A non-transitory computerreadable memory can also be referred to as a non-transitory computerreadable storage medium.

While particular combinations of various functions and features of theone or more embodiments have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A computer-implemented method of using acomputing system, the method comprises: interpreting, by a computingdevice of the computing system, a request to generate a non-fungibletoken (NFT) for an object distributed ledger to produce baseline contentthat includes an obligation provider identifier (ID) and an outcomerecipient ID, wherein the obligation provider ID is associated withproviding of an obligation tied to an obligation recipient ID inaccordance with obligation requirements, wherein the outcome recipientID is associated with a result of a triggered outcome tied to an outcomeprovider ID in accordance with contingent outcome rules and anobligation status, wherein a positive obligation status indicates thatthe obligation has historically been provided in accordance with theobligation requirements; verifying, by the computing device, with anaccreditation authority computing device of the computing system,validity of the baseline content; and when the baseline content isvalid: determining, by the computing device, whether a beneficialimprovement is provided to the result of the triggered outcome when ahypothetical change to the obligation provider ID is made, wherein thedetermining whether the beneficial improvement is provided includesproducing: an obligation evaluation based on an evaluation profile,wherein the obligation evaluation compares the providing of theobligation in accordance with the obligation requirements with thehypothetical change to the obligation provider ID, and an outcomeevaluation, wherein the outcome evaluation estimates the result of thetriggered outcome based on the evaluation profile when the hypotheticalchange to the obligation provider ID is made; establishing, by thecomputing device, NFT content based on the outcome evaluation to includethe baseline content; and causing, by the computing device, generationof a new block affiliated with the NFT via a blockchain of the objectdistributed ledger, wherein the new block includes the NFT content. 2.The method of claim 1, wherein the interpreting the request to generatethe NFT to produce the baseline content comprises: extracting, from therequest to generate the NFT, one or more of a contingency entity ID, theoutcome provider ID, a value of the result of the triggered outcome,obligation requirements, and the obligation recipient ID; determiningthe outcome recipient ID based on the request to generate the NFT andbenefactor information; and determining the obligation provider ID basedon the request to generate the NFT and debtor information.
 3. The methodof claim 1, wherein the verifying the validity of the baseline contentcomprises: identifying the accreditation authority computing devicebased on a first identified corresponding accreditation authorityassociated with the obligation recipient ID; obtaining baselinevalidation information from the accreditation authority computing devicefor the baseline content; and indicating that the baseline content isvalid when the baseline validation information is substantially the sameas the baseline content.
 4. The method of claim 1, wherein thedetermining whether the beneficial improvement is provided to the resultof the triggered outcome when the hypothetical change to the obligationprovider ID is made comprises: generating an obligation disruption riskassessment for the obligation provider ID based on the evaluationprofile to produce a baseline obligation evaluation; generating anotherobligation disruption risk assessment for the hypothetical change to theobligation provider ID based on the evaluation profile to produce ahypothetical baseline obligation evaluation; generating a baselineoutcome evaluation to include an estimate of the result of the triggeredoutcome utilizing the baseline obligation evaluation; generating theoutcome evaluation to include another estimate of the result of thetriggered outcome utilizing the hypothetical baseline obligationevaluation; and indicating that the beneficial improvement is providedto the result of the triggered outcome when the hypothetical change tothe obligation provider ID is made when the outcome evaluation isgreater than the baseline outcome evaluation.
 5. The method of claim 1,wherein the establishing the NFT content based on the outcome evaluationto include the baseline content comprises: generating the NFT content toinclude the baseline content; and updating the NFT content to replacethe obligation provider ID with an updated obligation provider IDassociated with the hypothetical change to the obligation provider IDwhen the beneficial improvement is provided to the result of thetriggered outcome from the hypothetical change to the obligationprovider ID.
 6. The method of claim 1, wherein the causing generation ofthe new block affiliated with the NFT via the blockchain of the objectdistributed ledger comprises: determining whether to indirectly ordirectly update the object distributed ledger; when indirectly updatingthe object distributed ledger: issuing a blockchain update request to anobject ledger computing device of the computing system serving as ablockchain node of the object distributed ledger, wherein the blockchainupdate request includes the NFT; and when directly updating the objectdistributed ledger: obtaining a copy of the object distributed ledger,hashing the NFT content of the NFT utilizing a receiving public key ofthe object distributed ledger to produce a next transaction hash value,encrypting the next transaction hash value utilizing a private key ofthe computing device to produce a next transaction signature, generatinga next block of the blockchain of the object distributed ledger toinclude the NFT content and the next transaction signature, and causinginclusion of the next block as the new block in the object distributedledger.
 7. A computing device of a computing system, the computingdevice comprises: an interface; a local memory; and a processing moduleoperably coupled to the interface and the local memory, wherein theprocessing module functions to: interpret a request to generate anon-fungible token (NFT) for an object distributed ledger to producebaseline content that includes an obligation provider identifier (ID)and an outcome recipient ID, wherein the obligation provider ID isassociated with providing of an obligation tied to an obligationrecipient ID in accordance with obligation requirements, wherein theoutcome recipient ID is associated with a result of a triggered outcometied to an outcome provider ID in accordance with contingent outcomerules and an obligation status, wherein a positive obligation statusindicates that the obligation has historically been provided inaccordance with the obligation requirements; verify with anaccreditation authority computing device of the computing system,validity of the baseline content; and when the baseline content isvalid: determine whether a beneficial improvement is provided to theresult of the triggered outcome when a hypothetical change to theobligation provider ID is made, wherein the processing module determineswhether the beneficial improvement is provided by producing: anobligation evaluation based on an evaluation profile, wherein theobligation evaluation compares the providing of the obligation inaccordance with the obligation requirements with the hypothetical changeto the obligation provider ID, and an outcome evaluation, wherein theoutcome evaluation estimates the result of the triggered outcome basedon the evaluation profile when the hypothetical change to the obligationprovider ID is made; establish NFT content based on the outcomeevaluation to include the baseline content; and cause generation of anew block affiliated with the NFT via a blockchain of the objectdistributed ledger, wherein the new block includes the NFT content. 8.The computing device of claim 7, wherein the processing module functionsto interpret the request to generate the NFT to produce the baselinecontent by: extracting, from the request to generate the NFT, one ormore of a contingency entity ID, the outcome provider ID, a value of theresult of the triggered outcome, obligation requirements, and theobligation recipient ID; determining the outcome recipient ID based onthe request to generate the NFT and benefactor information; anddetermining the obligation provider ID based on the request to generatethe NFT and debtor information.
 9. The computing device of claim 7,wherein the processing module functions to verify the validity of thebaseline content by: identifying the accreditation authority computingdevice based on a first identified corresponding accreditation authorityassociated with the obligation recipient ID; obtaining, via theinterface, baseline validation information from the accreditationauthority computing device for the baseline content; and indicating thatthe baseline content is valid when the baseline validation informationis substantially the same as the baseline content.
 10. The computingdevice of claim 7, wherein the processing module functions to determinewhether the beneficial improvement is provided to the result of thetriggered outcome when the hypothetical change to the obligationprovider ID is made by: generating an obligation disruption riskassessment for the obligation provider ID based on the evaluationprofile to produce a baseline obligation evaluation; generating anotherobligation disruption risk assessment for the hypothetical change to theobligation provider ID based on the evaluation profile to produce ahypothetical baseline obligation evaluation; generating a baselineoutcome evaluation to include an estimate of the result of the triggeredoutcome utilizing the baseline obligation evaluation; generating theoutcome evaluation to include another estimate of the result of thetriggered outcome utilizing the hypothetical baseline obligationevaluation; and indicating that the beneficial improvement is providedto the result of the triggered outcome when the hypothetical change tothe obligation provider ID is made when the outcome evaluation isgreater than the baseline outcome evaluation.
 11. The computing deviceof claim 7, wherein the processing module functions to establish the NFTcontent based on the outcome evaluation to include the baseline contentby: generating the NFT content to include the baseline content; andupdating the NFT content to replace the obligation provider ID with anupdated obligation provider ID associated with the hypothetical changeto the obligation provider ID when the beneficial improvement isprovided to the result of the triggered outcome from the hypotheticalchange to the obligation provider ID.
 12. The computing device of claim7, wherein the processing module functions to cause generation of thenew block affiliated with the NFT via the blockchain of the objectdistributed ledger by: determining whether to indirectly or directlyupdate the object distributed ledger; when indirectly updating theobject distributed ledger: issuing, via the interface, a blockchainupdate request to an object ledger computing device of the computingsystem serving as a blockchain node of the object distributed ledger,wherein the blockchain update request includes the NFT; and whendirectly updating the object distributed ledger: obtaining, via theinterface, a copy of the object distributed ledger, hashing the NFTcontent of the NFT utilizing a receiving public key of the objectdistributed ledger to produce a next transaction hash value, encryptingthe next transaction hash value utilizing a private key of the computingdevice to produce a next transaction signature, generating a next blockof the blockchain of the object distributed ledger to include the NFTcontent and the next transaction signature, and causing, via theinterface, inclusion of the next block as the new block in the objectdistributed ledger.
 13. A non-transitory computer readable memorycomprises: a first memory element that stores operational instructionsthat, when executed by a processing module of a computing device, causesthe processing module to: interpret a request to generate a non-fungibletoken (NFT) for an object distributed ledger to produce baseline contentthat includes an obligation provider identifier (ID) and an outcomerecipient ID, wherein the obligation provider ID is associated withproviding of an obligation tied to an obligation recipient ID inaccordance with obligation requirements, wherein the outcome recipientID is associated with a result of a triggered outcome tied to an outcomeprovider ID in accordance with contingent outcome rules and anobligation status, wherein a positive obligation status indicates thatthe obligation has historically been provided in accordance with theobligation requirements; a second memory element that stores operationalinstructions that, when executed by the processing module, causes theprocessing module to: verify with an accreditation authority computingdevice of a computing system, validity of the baseline content; and athird memory element that stores operational instructions that, whenexecuted by the processing module, causes the processing module to: whenthe baseline content is valid: determine whether a beneficialimprovement is provided to the result of the triggered outcome when ahypothetical change to the obligation provider ID is made, wherein theprocessing module determines whether the beneficial improvement isprovided by producing: an obligation evaluation based on an evaluationprofile, wherein the obligation evaluation compares the providing of theobligation in accordance with the obligation requirements with thehypothetical change to the obligation provider ID, and an outcomeevaluation, wherein the outcome evaluation estimates the result of thetriggered outcome based on the evaluation profile when the hypotheticalchange to the obligation provider ID is made; establish NFT contentbased on the outcome evaluation to include the baseline content; andcause generation of a new block affiliated with the NFT via a blockchainof the object distributed ledger, wherein the new block includes the NFTcontent.
 14. The non-transitory computer readable memory of claim 13,wherein the processing module functions to execute the operationalinstructions stored by the first memory element to cause the processingmodule to interpret the request to generate the NFT to produce thebaseline content by: extracting, from the request to generate the NFT,one or more of a contingency entity ID, the outcome provider ID, a valueof the result of the triggered outcome, obligation requirements, and theobligation recipient ID; determining the outcome recipient ID based onthe request to generate the NFT and benefactor information; anddetermining the obligation provider ID based on the request to generatethe NFT and debtor information.
 15. The non-transitory computer readablememory of claim 13, wherein the processing module functions to executethe operational instructions stored by the second memory element tocause the processing module to verify the validity of the baselinecontent by: identifying the accreditation authority computing devicebased on a first identified corresponding accreditation authorityassociated with the obligation recipient ID; obtaining baselinevalidation information from the accreditation authority computing devicefor the baseline content; and indicating that the baseline content isvalid when the baseline validation information is substantially the sameas the baseline content.
 16. The non-transitory computer readable memoryof claim 13, wherein the processing module functions to execute theoperational instructions stored by the third memory element to cause theprocessing module to determine whether the beneficial improvement isprovided to the result of the triggered outcome when the hypotheticalchange to the obligation provider ID is made by: generating anobligation disruption risk assessment for the obligation provider IDbased on the evaluation profile to produce a baseline obligationevaluation; generating another obligation disruption risk assessment forthe hypothetical change to the obligation provider ID based on theevaluation profile to produce a hypothetical baseline obligationevaluation; generating a baseline outcome evaluation to include anestimate of the result of the triggered outcome utilizing the baselineobligation evaluation; generating the outcome evaluation to includeanother estimate of the result of the triggered outcome utilizing thehypothetical baseline obligation evaluation; and indicating that thebeneficial improvement is provided to the result of the triggeredoutcome when the hypothetical change to the obligation provider ID ismade when the outcome evaluation is greater than the baseline outcomeevaluation.
 17. The non-transitory computer readable memory of claim 13,wherein the processing module functions to execute the operationalinstructions stored by the third memory element to cause the processingmodule to establish the NFT content based on the outcome evaluation toinclude the baseline content by: generating the NFT content to includethe baseline content; and updating the NFT content to replace theobligation provider ID with an updated obligation provider ID associatedwith the hypothetical change to the obligation provider ID when thebeneficial improvement is provided to the result of the triggeredoutcome from the hypothetical change to the obligation provider ID. 18.The non-transitory computer readable memory of claim 13, wherein theprocessing module functions to execute the operational instructionsstored by the third memory element to cause the processing module tocause generation of the new block affiliated with the NFT via theblockchain of the object distributed ledger by: determining whether toindirectly or directly update the object distributed ledger; whenindirectly updating the object distributed ledger: issuing a blockchainupdate request to an object ledger computing device of the computingsystem serving as a blockchain node of the object distributed ledger,wherein the blockchain update request includes the NFT; and whendirectly updating the object distributed ledger: obtaining a copy of theobject distributed ledger, hashing the NFT content of the NFT utilizinga receiving public key of the object distributed ledger to produce anext transaction hash value, encrypting the next transaction hash valueutilizing a private key of the computing device to produce a nexttransaction signature, generating a next block of the blockchain of theobject distributed ledger to include the NFT content and the nexttransaction signature, and causing inclusion of the next block as thenew block in the object distributed ledger.